Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Status
titleREVIEWED 240531

The Drupal Association has introduced the use of gitlab-ci for running tests and other code analysis on Drupal modules. This blog post is an excellent guide for getting up and running with gitlab-ci. There is also some good documentation here. Here are the basic steps:

...

If cspell identifies spelling errors that should not be flagged (e.g. Kalamuna) you can add a file named .cspell-project-words.txt to your project root, with one word to be ignored by the spell checker per line.

Remove DrupalCI Schedules

The final step in removing the dependency on DrupalCI is to remove any automated tests runs scheduled.

  1. Visit your module page and look at the releases on offer. Ensure that all of those branches have Gitlab CI enabled if needed.

  2. Look for an Automated testing tab.

    Image Added

  3. Click into that tab and under the DrupalCI (deprecated) section, click on “delete all DrupalCI testing schedules” and confirm on the next screen.

    Image Added

  4. You should now see your module page with no Automated testing tab. Gitlab pipeline information can now be found on each release card.

    Image Added

...

Review History

Who

When

Status

Bob

20250531

Finished final draft