Michael Anello Explores GitLab CI for Drupal Module Testing

Staff Reporter

Michael Anello recently shared an insightful blog post on DrupalEasy, shedding light on the general availability of GitLab CI (Continuous Integration) for Drupal-contributed modules. This collaborative effort by the Drupal Association (DA) and various community contributors aims to revolutionize the way automated tests are conducted for both Drupal core and contributed projects.

The primary goal of this initiative is to replace the existing, bespoke Drupal CI with GitLab's CI tools, offering a more efficient and resource-saving solution for the long term. Module maintainers, in particular, stand to benefit significantly, gaining the ability to specify more flexible tests and code validations tailored to the unique needs of their projects.

The heart of this project lies in the implementation of GitLab templates, providing module maintainers with a robust starting point for their testing processes. For each commit to a contributed module project, GitLab CI will execute a maintainer-defined process, conducting various checks on the code. These checks encompass crucial steps such as validating the project's composer.json file, performing coding standard checks via phpcs, and executing static code analysis checks via PhpStan. Additionally, testing steps will be incorporated, running the module's PhpUnit tests in different Drupal environments, encompassing various versions of Drupal core and PHP.

Michael Anello highlighted the ongoing efforts in the Drupal community to optimize and enhance GitLab CI templates. Regular GitLab Acceleration Initiative meetings take place in the #gitlab channel of the Drupal Slack workspace, providing a collaborative space for contributors. The issue queue serves as a central hub for community-driven work, encouraging individuals to file new issues, collaborate on existing ones, and contribute to testing efforts.

Recent strides in this initiative include the addition of features like PhpStan support and Drupal 7 compatibility to the default templates. The community is actively exploring ways to further optimize the pipeline, both in terms of speed and resource efficiency.

For a detailed overview of this exciting development, interested readers are encouraged to delve into Michael Anello's blog post on DrupalEasy. The Drupal community's embrace of GitLab CI marks a significant step forward in streamlining testing processes and fortifying the robustness of contributed modules.

Image Attribution Disclaimer: At The Drop Times (TDT), we are committed to properly crediting photographers whose images appear in our content. Many of the images we use come from event organizers, interviewees, or publicly shared galleries under CC BY-SA licenses. However, some images may come from personal collections where metadata is lost, making proper attribution challenging.

Our purpose in using these images is to highlight Drupal, its events, and its contributors—not for commercial gain. If you recognize an image on our platform that is uncredited or incorrectly attributed, we encourage you to reach out to us at #thedroptimes channel on Drupal Slack.

We value the work of visual storytellers and appreciate your help in ensuring fair attribution. Thank you for supporting open-source collaboration!

Michael Anello

GitLab

Drupal Modules

Drupal Community

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 reach out to us at #thedroptimes channel on Drupal Slack and we will try to address the issue as best we can.