Problem/Motivation

Since 7th of June, 2023, Drupal.org enabled GitLab CI for testing purposes. GitLab CI is now preferred over DrupalCI for testing. We need to remove DrupalCI testing once you have GitLab CI set up.

This issue is to track progress towards getting a .gitlab-ci.yml file so that we can migrate away from the deprecated DrupalCI to GitLab CI.

Proposed resolution

Add default .gitlab-ci.yml

Issue fork reroute_email-3390104

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

bohart created an issue. See original summary.

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

Abyss opened merge request !48

abyss’s picture

abyss commented
Status: Active » Needs review

Added default .gitlab-ci.yml.

  • bohart committed 2248c490 on 2.2.x authored by Abyss 
    Issue #3390104: setup GitLab CI pipelines (added .gitlab-ci.yml file).

Abyss opened merge request !49

Abyss opened merge request !52

  • bohart committed d86135f9 on 2.2.x authored by Abyss 
    Issue #3390104: Replaced DrupalCI testing with GitLab CI pipelines.

  • bohart committed a866fc9e on 2.1.x authored by Abyss 
    Issue #3390104: Replaced DrupalCI testing with GitLab CI pipelines.
bohart’s picture

bohart
Location Lutsk, Ukraine
commented
Status: Needs review » Fixed

Committed to both 2.1.x (^D8.8 & <=D9.3) and 2.2.x (^9.4 || ^10) branches.
So the module will handle proper testing for the needed Drupal and PHP versions in them.

This will be a part of the next releases of the module soon.
Thanks @all!

Status: Fixed » Closed (fixed)

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