Using GitLab CI instead of Drupal CI

Is it possible that projects would be able to opt into test coverage without adding the file, that a systemwide default file could be used if one isn't present?

No, GitLab CI is not centralized like DrupalCI. A maintainer has to commit their .gitlab-ci.yml file. In the future, templates may reduce what needs to be in that file, but its existence is necessary. We have not made commits on maintainers’ behalf, other than the Great Git Migration, which was required for technical differences from CVS.

Good to know, thanks for the explanation, drumm.

Has anyone compiled a list of limitations yet? For example, is it possible to run multiple test pipelines with different releases of core, PHP and MySQL?

Would like to use gitlab ci on the select2 project as soon as the next round starts. Thx

Would like to test Gitlab CI on the https://www.drupal.org/sandbox/bhanu951/3103712 project as soon as the next round starts. Thanks.

As we successfully run GitLab CI on Gin Admin Theme now, I'd also like to opt in for it's modules, https://www.drupal.org/project/gin_toolbar & https://www.drupal.org/project/gin_login
TY!

I'd like to opt in with https://www.drupal.org/project/cdn :)

Bhanu951 - sandbox projects will likely never have GitLab CI available, #3204605: Phase out sandbox projects

Noting here, had a great conversation with @karinG about drupal.org/project/webform_civicrm opting in - they have already fully adopted github actions and other pipelines and would love to port it over to our official solution, and help us test this out.

Updating list of projects with GitLab CI enabled.

I'd like to opt https://www.drupal.org/project/distributions_recipes in. It's going to need to run a small subset of core tests against that project's 10.x branch.

I'd like to opt in with https://git.drupalcode.org/project/omdb_api . Thanks.

https://www.drupal.org/project/distributions_recipes is a general project, all general projects have GitLab CI available automatically.

omdb_api now has GitLab CI enabled.

Hello, can we get https://www.drupal.org/project/anu_lms enrolled into GitLab CI as well please? This is what keeps the project still on Github instead of Drupal.org. Thanks :)

Would it be possible to enable Gitlab CI on https://www.drupal.org/project/next_webform?

next_webform is a general project. All general projects have GitLab CI enabled.

anu_lms now has GitLab CI enabled.

Please add the following projects to opt in:

- https://www.drupal.org/project/migrate_visualize
- https://www.drupal.org/project/advancedform

Thanks!

PS. I had to go look up "general project" as I hadn't heard the term before. For anyone else wondering:

A general project is anything that is not a module, theme, or other more-specific project type that is managed on Drupal.org.

migrate_visualize & advancedform now have GitLab CI enabled.

I'd like to opt in for the file_delete module.

https://www.drupal.org/project/file_delete

Thanks!

Hello,

I would like to opt-in for File Extractor https://www.drupal.org/project/file_extractor please.

Thanks!

file_delete & file_extractor now have GitLab CI enabled

Can you please add https://www.drupal.org/project/webprofiler ?

Thanks!

Could I opt the following in?

https://drupal.org/project/lightning_core
https://drupal.org/project/lightning_api
https://drupal.org/project/lightning_media
https://drupal.org/project/lightning_wokflow
https://drupal.org/project/lightning_layout

Can we opt-in https://www.drupal.org/project/material_base please? We would like to use Gitlab pages for automated building of the documentation from md files inside the repo.

webprofiler, lightning_core, lightning_api, lightning_media, lightning_workflow, lightning_layout & material_base now have GitLab CI enabled.

paragraphs_features would also like to use the Gitlab CI

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

yoast_seo would also like to use the GitLab CI

https://www.drupal.org/project/geolocation please

Happy New Year wonderful people!

We would love to test the CI for our LocalGov Drupal distributions, in the hope that we can move active development back from Github to drupal.org with automated tests and code review etc.

The two main projects are:

https://www.drupal.org/project/localgov
https://www.drupal.org/project/localgov_microsites

Many thanks!

Finn

yoast_seo, geolocation, localgov & localgov_microsites now have GitLab CI enabled.

Request to opt in: simpleSAMLphp Authentication

to work around a composer plugin restriction, per: #3334914: Testing is broken because simplesamlphp/composer-module-installer contains a Composer plugin which is blocked

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. 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/cache_metrics. 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!