Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
By hestenet on
Change record status:
Published (View all published change records)
Project:
Description:
We have been making some improvements to DrupalCI in order to accommodate several broad categories of architectural improvements and feature requests, as summarized in the DrupalCI roadmap. Some highlights include:
- Ability to Build projects that have external composer dependencies
- Projects are built using composer and the composer facade
- Patches applied to composer.json will cause a recalculation of dependencies (meaning dependency changes can be submitted in the patch)
- Dependencies rely on composer, so if a developer wants granular control over *which* dependencies are tested, they can add a composer.json to their project and specify exactly which deps.
- ‘Require-dev’ of tested dependencies will also be downloaded.
- More artifacts available post test to determine root cause of failures (see jenkins)
- Repeatable build file that can be downloaded to a local drupalci instance and re-executed verbatum (remote config soon!)
- Patch names can no longer interfere with tests accidentally
- Database containers are no longer persistent and shared between tests. All containers are created and destroyed per test
- Containers and environments split from the testrunner codebase
- Container images are pulled if they are not already local
- DrupalCI and all dependencies upgraded to use php7 compatible code
- all database interaction happens through PDO
Next steps include further review and testing of these changes, as well as documenting the changes and the contribution process.
Production outage: No
Change affects: DrupalCI
Deployment schedule: To be deployed in December
Backout plan: revert or fix in place