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/ckeditor_details/-/pipelines
 

The module doesn't have any automated tests so far (PHPUNIT), but we could definitely use the validation jobs: CSPELL, ESLINT, PHPCS, PHPSTAN and STYLELINT.

This would be very helpful to refine the work submitted in merge pending requests.

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!

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:

Comments

dydave created an issue. See original summary.

dydave’s picture

Priority: Normal » Major
Status: Active » Needs review

Quick follow-up on this issue:

Created the merge request MR !7 above at #2 which adds an initial .gitlab-ci.yml file to automate builds on GitlabCI.

Added the bare minimum configuration to enable automated build pipelines with all validation jobs:
cspell, eslint, phpcs, phpstan and stylelint.
Left all the variables and custom jobs configuration code commented, so it could be enabled in the future (uncommented).

This is left completely at the appreciation and preference of the project maintainers: feel free to adjust the file as you would see fit.

The merge request build came back with errors for all jobs, but fixing them should be considered out-of-scope in this issue.
Fixing validation jobs should be addressed in separate tickets.

Bumping issue to Major as this task should be very straight forward and unblock the validation of all pending merge requests.

Moving issue to Needs review as an attempt to attract the attention of project's maintainer and collect more feedback.
Thanks in advance!

liam morland made their first commit to this issue’s fork.

liam morland’s picture

Status: Needs review » Fixed

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.

dydave’s picture

Thanks a lot Liam (@liam morland) for taking care of this issue.

Any chance you could update this issue's contribution records and grant me credit?
This is mostly to record the contribution for the company on whose behalf the code changes were contributed.

Thanks in advance!

liam morland’s picture

Done

dydave’s picture

Super nice Liam!
Thanks a lot! 🙏

  • liam morland committed 055ff364 on 2.1.x
    fix: #3525045 Inject StringTranslationTrait into DetailPlugin
    
    Fixes...

  • liam morland committed 055ff364 on 2.x
    fix: #3525045 Inject StringTranslationTrait into DetailPlugin
    
    Fixes...

Status: Fixed » Closed (fixed)

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