Problem/Motivation

Add CI/CD GitLab pipeline.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork iconset-3518854

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

bluegeek9 created an issue. See original summary.

bluegeek9 opened merge request !6

bluegeek9 opened merge request !7

bluegeek9’s picture

bluegeek9 commented
Assigned: bluegeek9 » Unassigned
Status: Active » Needs review
lemming’s picture

lemming commented
Assigned: Unassigned » lemming

Thanks for suggesting this.

I need read the documentation on the settings that they have provided for the CI/CD process since they moved away from providing the DrupalCI testing processes.

Do you happen to know what the triggers are for testing with this CI/CD configuration? Previously there was the ability to retest based on a schedule (i.e. Weekly) and set the DB & Drupal versions to run the tests with.

Does this only trigger on code pushes and deploys? New version of Drupal core releases?

bluegeek9’s picture

bluegeek9 commented

The pipeline runs with every MR.

In gitlab you can configure a test schedule. I recommend testing weekly.

https://git.drupalcode.org/project/iconset/-/pipeline_schedules

lemming’s picture

lemming commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

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