Problem/Motivation

In order to replace DrupalCI with GitLab CI we need to ensure we have feature parity between the two systems. Following #3386076: GitLab CI integration for core a number of followups have been opened for other features that we did not build in the initial proof-of-concept. This issue exists as a parent to track all child issues in one place.

Steps to reproduce

Proposed resolution

Remaining tasks

Blockers for switching of Drupal CI for public core tests

#3386566: Add support for 'test only' changes to gitlab CI
#3387748: Gitlab jobs fail on 302 redirect from git
#3385620: [GitlabCI] SQLite currently not working
#3385621: [GitlabCI] MariaDB currently not working
#3387927: Failing Nightwatch jobs result in a passed pipeline job
#3398896: Keep the ability to search emailed reports for random test failures

User interface changes

API changes

Data model changes

Release notes snippet

Comments

longwave created an issue. See original summary.

catch’s picture

catch
he/him
Primary language English
commented
Issue summary: View changes
quietone’s picture

quietone commented

By the titles of the child issues I don't see one for keeping the ability to not test a change. Is that possible?

catch’s picture

catch
he/him
Primary language English
commented

@quietone it's not possible yet but it might be possible with MR tags and/or the draft status, worth opening an issue.

quietone’s picture

quietone commented
Issue summary: View changes

I added #3398896: Keep the ability to search emailed reports for random test failures as a blocker, unless of course, there is another way to get statistics on individual test failures.

ressa’s picture

ressa
he/him
commented

Perhaps a new issue Component "Gitlab CI" can be created, for this and other Gitlab CI issues?

Also, some module maintainers are having trouble switching to Gitlab CI (see for example #3395901: Use Gitlab CI in Simplenews) so I wonder if there is a meta issue, where project maintainers can discuss problems and solutions, like there is #2829040: [meta] Known intermittent, random, and environment-specific test failures for test failures. Similarly, in a new issue ("[Meta] Switching to Gitlab CI"?) module maintainers could share a link to the "Switch to Gitlab CI" issue for their project, and discuss solutions with other maintainers.

catch’s picture

catch
he/him
Primary language English
commented
Component: other » phpunit

@ressa for contrib probably an issue in https://www.drupal.org/project/gitlab_templates would be best?

I've just been using the phpunit component for gitlab issues which is not a 1-1 match but has been working well enough, I think we should rename that to testing (so it covers nightwatch and linting too as well as gitlab) rather than add a new one - but it's not easy to rename components on d.o iirc.

ressa’s picture

ressa
he/him
commented
Related issues: +#3424725: [Meta] Switching contrib modules to Gitlab CI

Thanks for the feedback @catch I have created #3424725: [Meta] Switching contrib modules to Gitlab CI.

And about "phpunit", I also noticed many Gitlab CI issues are using that, and thought - "hmm, what if Drupal switch to Cypress, or something else?" so a generic "testing" seems like the logical solution. But I can imagine updating an existing Component name may be a challenge ...

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.