Using GitLab CI instead of Drupal CI

Requesting to opt-in redis module.

Needs two php extensions installed to connect to a redis container.

@berdir is a maintainer and is OK with it. See https://drupal.slack.com/archives/C1BMUQ9U6/p1674582990176319?thread_ts=...

https://www.drupal.org/project/simplesamlphp_auth → & https://www.drupal.org/project/redis → now have GitLab CI enabled.

Request to opt-in https://www.drupal.org/project/examples → thanks!

Akamai module needs to opt in as its Composer setup can't work on DrupalCI. This is needed for D10 support. See https://www.drupal.org/project/akamai/issues/3337078#comment-14968641 📌 Drupal 10 compatibility Fixed . Thanks.

I'd like to spend some time working on evaluating how phpstan, code coverage reporting, and possibly pipeline triggers can be integrated into the current template workflows, to that end can I opt in the Vault module and its related ecosystem modules:

(mostly have the first two already working in a local lab, though would be good to test on the real D.O. environment and work with updating the templates to make it easier)

https://www.drupal.org/project/vault →
https://www.drupal.org/project/vault_auth_approle →
https://www.drupal.org/project/vault_key_aws →
https://www.drupal.org/project/vault_key_kv →
https://www.drupal.org/project/vault_auth_token →
https://www.drupal.org/project/encrypt_vault_transit →

These projects now have GitLab CI enabled. Please be sure to include a link directly to the project when requesting, so we don’t have to look for it

https://www.drupal.org/project/examples →
https://www.drupal.org/project/vault →
https://www.drupal.org/project/vault_auth_approle →
https://www.drupal.org/project/vault_key_aws →
https://www.drupal.org/project/vault_key_kv →
https://www.drupal.org/project/vault_auth_token →
https://www.drupal.org/project/encrypt_vault_transit →
https://www.drupal.org/project/akamai →

Request to opt-in https://www.drupal.org/project/examples → . Thanks.

https://www.drupal.org/project/cache_metrics → now has GitLab CI enabled

I would like to opt-in following modules to boost D10 compatibility efforts:

https://www.drupal.org/project/commerce_availability_notification →
https://www.drupal.org/project/commerce_logistra →
https://www.drupal.org/project/commerce_item_discount_ui →
https://www.drupal.org/project/commerce_vipps →

commerce_availability_notification, commerce_logistra, commerce_item_discount_ui & commerce_vipps now have GitLab CI enabled.

Request to opt-in Scheduler https://www.drupal.org/project/scheduler →
Thanks

scheduler now has GitLab CI enabled.

Could you please opt-in https://www.drupal.org/project/youtube → ? Thank you!

https://www.drupal.org/project/youtube → now has GitLab CI enabled.

https://www.drupal.org/project/entitygroupfield → please, thanks!

https://www.drupal.org/project/entitygroupfield → now has GitLab CI enabled

@drumm
We would love to have Gitlab CI enabled for our project:
https://www.drupal.org/project/graphql_core_schema →

We plan to automatically build the documentation on Netlify.

I want to use Gitlab CI for https://www.drupal.org/project/search_api_solr → to replace our github Actions workaround.

https://www.drupal.org/project/graphql_core_schema → & https://www.drupal.org/project/search_api_solr → now have GitLab CI enabled.

There was still one more reference to the closed alpha, so I took the liberty to make some more adjustments to the IS.

I want to use Gitlab CI for https://www.drupal.org/project/search_api_field_token →

All full projects on Drupal.org can now use GitLab CI!

All full projects on Drupal.org can now use GitLab CI!

Can you explain how to activate it? I've added a .gitlab-ci.yml file in an open issue fork on a full project. The yml validates when checked in the Pipeline Editor in gitlab but when trying to run it with the "Validate" tab I see "Pipelines are disabled!". I also don't see a CI tab on the left menu anywhere. According to the docs page it says:

When you first commit your .gitlab-ci.yml file the pipeline should be triggered automatically.

1. Navigate to the sidebar
2. Click on 'CI/CD'
3. Click on 'Pipelines'

I don't see CI/CD anywhere or Pipelines in the sidebar.

The .gitlab-ci.yml file needs to be committed to the project to be active

FYI it appears that GitlabCI pipelines can be activated on issue fork repos. However I had to push .gitlab-ci.yml to the 'main' / default branch, rather than the issue branch within the issue fork repo, before it would 'see' that gitlabCI should be available. After that it works fine.

I believe we can call this done now. Thanks everyone!

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