Drupal's GitLab CI Testing Achieves Fivefold Speed Boos
Drupal core's GitLab CI testing has achieved a remarkable milestone—testing is now five times faster than its predecessor, DrupalCI. This transition represents a major leap in development efficiency and aligns with Drupal's commitment to staying at the forefront of web development practices.
The journey towards this achievement commenced five years ago when Drupal migrated its code hosting to GitLab. However, moving testing from the home-grown DrupalCI to GitLab CI has been a gradual and strategic process. The culmination of this endeavour brings forth a more streamlined and expedited testing experience for all developers working on code within the Drupal community.
Announcement of Crucial Changes and Future Plans
Gábor Hojtsy recently published a comprehensive blog post on Drupal.org, shedding light on several vital changes and future plans that will impact developers working on Drupal.org.
One of the pivotal updates pertains to contributed projects. Starting from July 2023, all contributed projects are encouraged to embrace GitLab CI. This move signifies Drupal's commitment to modernizing its development practices and ensures that contributed projects align with the evolving landscape of web development.
Retirement of DrupalCI on the Horizon
While DrupalCI has played an integral role in the Drupal development process, it is essential to adapt to more efficient testing methods. As part of this transition, the DrupalCI system will be gradually retired, but not without ensuring a seamless handover of its functionalities to GitLab CI. Although a specific retirement date has not been finalized, the Drupal community is committed to completing this transition within a year.
Testing Core: A Fivefold Boost in Speed
One of the most notable outcomes of this transition is the remarkable improvement in core testing speed. GitLab CI's configuration for core testing has been meticulously adapted to provide a more modern and significantly faster testing environment. In contrast to Drupal CI, where core testing runs would take just over 50 minutes, GitLab CI can execute the same test suite in under ten minutes, a fivefold increase in efficiency.
Developers working on core issues will benefit from these improvements when filing merge requests in GitLab. Furthermore, GitLab CI's user-friendly interface streamlines the process of identifying coding standard violations or test failures, enabling developers to pinpoint issues swiftly and efficiently.
Additionally, GitLab CI offers an automated re-run feature for jobs that encounter issues outside of the tests, such as timeouts or scheduling problems, with up to two retries. This feature eliminates the need to wait for the entire pipeline to complete, further enhancing the development workflow.
To delve deeper into these transformative changes and explore the enhanced capabilities of GitLab CI, developers and Drupal enthusiasts are encouraged to visit the comprehensive blog post authored by Gábor Hojtsy on drupal.org.
Disclaimer: The opinions expressed in this story do not necessarily represent that of TheDropTimes. We regularly share third-party blog posts that feature Drupal in good faith. TDT recommends Reader's discretion while consuming such content, as the veracity/authenticity of the story depends on the blogger and their motives.
Note: The vision of this web portal is to help promote news and stories around the Drupal community and promote and celebrate the people and organizations in the community. We strive to create and distribute our content based on these content policy. If you see any omission/variation on this please let us know in the comments below and we will try to address the issue as best we can.
Related People
Comments
You may also like
