- Issue created by @dydave
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
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!
Active
3.0
Code