[meta] GitLab CI feature parity with DrupalCI

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

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

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

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 📌 Use gitlab-ci Needs work ) so I wonder if there is a meta issue, where project maintainers can discuss problems and solutions, like there is 🌱 [meta] Known intermittent, random, and environment-specific test failures Active 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.

@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.

Thanks for the feedback @catch I have created #3424725: [Meta] Switching 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 ...