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 similar automated testing conditions: PHP, DB, Core versions, branches, triggers on commits, patches susbmitted 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/login_switch/-/pipelines
See existing tests configurations on modules's current automated testing page on DO.
 

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 login_switch-3497745

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.

deepali sardana’s picture

deepali sardana commented
Assigned: Unassigned »

dydave opened merge request !5

dydave’s picture

dydave commented
Assigned: » Unassigned
Status: Active » Needs review

Quick follow-up on this issue:

Added initial configuration of Gitlab CI pipelines with the most basic and minimal job requirements: Testing only for D10 for now.
Left a few commented sections that could be enabled down the road to broaden tests coverage and enforce certain jobs.

Moving issue to Needs review since the tests are passing:
https://git.drupalcode.org/issue/login_switch-3497745/-/pipelines/428064

with warnings, that should most likely be addressed in different tickets (out of scope in this issue).

We would greatly appreciate if a maintainer with write access could take a look at merge request MR!5 and let us know if any more work would be required to get automated tests pipelines configured in the code base on Gitlab.

Feel free to let us know if you would have any questions or concerns on any aspects of this issue or the project in general, we would surely be glad to help.
Thanks in advance!

dydave changed the visibility of the branch 3497745-fix-phpcs to hidden.

  • drupalmatts committed 09e34bf9 on 8.x-dev authored by dydave 
    Issue #3497745 by DYdave: Automated testing on GitLab CI: Added initial...
dydave’s picture

dydave commented

Super nice Matthew (@drupalmatts)!!

Thanks a lot for the speedy reply and for getting this in, it's super appreciated!

Any chance we could get a word from you on #3499850-5: Add module configuration schema file
==> the dev branches are confusing ... for creating MRs and such...

+ possibly the co-maintainer offer #3507910: Offering to co-maintain Login Switch
That's really up to you ... it's not like I don't have anything on my plate already 😅
But it would definitely allow to speed up the changes.

Cheers !

  • drupalmatts committed 68292030 on 8.x-3.x 
    Issue #3497745 by DYdave: Automated testing on GitLab CI: Added initial...

  • drupalmatts committed 68292030 on 3.x 
    Issue #3497745 by DYdave: Automated testing on GitLab CI: Added initial...