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: #3357190: Configure GitLab CI, 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!

Issue fork config_perms-3516579

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

About issue forks

Comments

dydave created an issue. See original summary.

dydave opened merge request !6

dydave’s picture

dydave commented
Status: Active » Needs review

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!

wylbur made their first commit to this issue’s fork.

mlncn’s picture

mlncn commented

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.

  • mlncn committed 6bd920d5 on 8.x-2.x 
    Issue #3516579 by wylbur, dydave, mlncn: Automated testing: Configure...
dydave’s picture

dydave commented

Understandable, thanks a lot Benjamin (@mlncn)!

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

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! 🙂

  • mlncn committed eacf6c5f on 8.x-2.x authored by dydave 
    Issue #3516579 by dydave: Automated testing on GitLab CI: Added initial...
mlncn’s picture

mlncn commented
Status: Needs review » Fixed

Brought everything in but not making passing the various code style tests required.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

mlncn closed merge request !6

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.