Contrib.social

Automated testing: Configure GitLab CI

Open on Drupal.org →
Created on 1 April 2025, 3 months ago

I found some helpful documentation on the topic: Documentation on Drupal.org: GitLab CI → .

Then, found the config file template:
https://git.drupalcode.org/project/gitlab_templates/-/blob/main/gitlab-c...

and then searched the entire DO project base:
https://git.drupalcode.org/search?group_id=2&scope=blobs&search=Gitlab-c...

which led to a relevant example: 📌 Configure GitLab CI Fixed , for the YouTube Field → module, which seems to have a reasonably good user base and checked its pipeline page, see:
https://git.drupalcode.org/project/youtube/-/pipelines
See code file: https://git.drupalcode.org/project/youtube/-/blob/2.x/.gitlab-ci.yml

Work expected:

Transition the project to use GitLab CI pipelines instead of DrupalCI, to provide automated testing conditions: PHP, DB, Core versions, branches, triggers on commits, patches submitted in tickets, etc...

1 - The "first step is to add a .gitlab-ci.yml file to the root of the project."

2 - Configure the Automated testing pipelines on GitLabCI at:
https://git.drupalcode.org/project/config_perms/-/pipelines
 

Feel free to let us know if you have any suggestions, comments, or feedback on this ticket or the project in general, we would be glad to help and provide more information.
Thanks in advance!

📌 Task
Status

Active

Version

2.0

Component

Code

Created by

🇫🇷France dydave

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @dydave
  • Merge request !6Issue #3516579 by dydave: Automated testing on GitLab CI: Added initial... → (Open) created by dydave
  • Pipeline finished with Success
    3 months ago
    Total: 184s
    #462271
  • Comment 3 months ago →
    🇫🇷France dydave

    Created initial merge request MR!6 above at #2 with minimal configuration to support automated testing on Gitlab CI.

    All PHPUnit tests seem to be passing so it should not be blocking any pending merge requests.

    Thus moving issue to Needs review.

    More changes to the Gitlab config file could be done in the future to broaden Tests coverage and/or require certain jobs to pass.

    Any comments, feedback and questions would be greatly appreciated.
    Thanks in advance!

  • First commit to issue fork.
  • Pipeline finished with Success
    about 1 month ago
    Total: 146s
    #504229
  • Pipeline finished with Success
    about 1 month ago
    Total: 146s
    #504248
  • Pipeline finished with Success
    about 1 month ago
    Total: 458s
    #504254
  • Comment about 1 month ago →
    🇺🇸United States mlncn Minneapolis, MN, USA

    OK it is great to have all the code to fix the GitLab CI complaints but we will take the CI config file as a first step here.

  • Comment about 1 month ago →
    System Message
    • mlncn → committed 6bd920d5 on 8.x-2.x 
      Issue #3516579 by wylbur, dydave, mlncn: Automated testing: Configure...
  • Comment about 1 month ago →
    🇫🇷France dydave

    Understandable, thanks a lot Benjamin (@mlncn)!

    I've create a follow-up issue to address all the validation errors on which Wylbur (@wylbur) has been working, see:
    📌 Gitlab CI: Fix validation errors reported by jobs CSPELL, PHPCS and PHPSTAN Active

    and moved all his work to MR !7 👌

    Any chance we could consider this particular issue Fixed, get credits assigned and move to the other issue?
    Maybe this ticket's merge request MR !6 could be closed now, since it's not going to go any further anyway?

    Any feedback, comments or questions would be greatly appreciated.
    Thanks in advance! 🙂

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024