To continue automated testing, projects must convert to GitLab CI and contributors must switch from patches to merge requests by July 1, 2024.
As of July 2023, contributed projects are fully equipped to adopt GitLab CI. In October 2023 we announced that Gitlab CI testing of Drupal core was already five times faster than the legacy DrupalCI system. In our December 2023 maintainer email we announced that our legacy DrupalCI will be retired as soon as July 2024. Now we are announcing further details.
What's happening?
Some DrupalCI features are already turned off
Projects without DrupalCI testing configured cannot add it anymore. Direct access to log output and artifacts on DrupalCI is no longer available. Results are still summarized on the Automated Testing tab of those project's pages.
With the exception of Drupal 7, it is not possible to run tests on patches against Drupal core anymore. Even for Drupal 7, patches need to be sent for testing manually.
Changing DrupalCI schedules ends on April 30, 2024
After April 30, 2024, DrupalCI schedules can not be added or changed, except to remove DrupalCI testing. Tests will keep running with existing configured schedules until removed.
DrupalCI and all patch testing will be turned off on July 1, 2024
No DrupalCI tests will be executed after this date. It will also no longer be possible to run tests on any patches on Drupal.org on any project. Existing test results will be kept for six months.
All results from DrupalCI tests will be removed on January 1, 2025
This is the end of DrupalCI data retention. No testing results will be available beyond January 1, 2025.
What to do about it?
Most projects can start GitLab CI testing with a provided template .gitlab-ci.yml
Using GitLab CI for testing may seem intimidating at first but the Drupal Association engineering team and a number of community volunteers have spent a lot of time to make it as easy as possible for you to adopt GitLab CI for testing.
There is a preconfigured .gitlab-ci.yml template that will set up everything you need to test your project. This template has several useful features, including a variables file that will be automatically updated by the Drupal Association, to make sure you’re always testing against the currently supported versions of Drupal.
Most project maintainers won’t have to make any changes to the template, just commit the template to your project and your testing should work right away!
Set up GitLab CI for your drupal.org project today.
Contributors must use merge requests on all projects to get automated testing after July 1, 2024
GitLab CI, like almost all modern CI systems, is designed to test merge requests. If you have ever contributed to a project on GitHub, you pretty much already know how it works. The advantage of Drupal.org merge requests is that they are collaborative by default, so you and fellow contributors can work in the same fork.
Read the best practices for contributing through merge requests.