Problem/Motivation
The first jobs listed in gitlabci.yml run first in gitlab. This can impact the order they get allocated a pod etc. The UI is alphabetical so it only affects the running order, not anything else.
Currently phpstan tends to be the slowest linting job, and component unit tests take longer than core unit tests.
The improvement here is likely to be a 1-10 seconds at most, but it's also very easy to move a chunk of code, so development time to annual CI runtime is still going to gain many hundreds of seconds.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
Introduced terminology
API changes
Data model changes
Release notes snippet
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | Screenshot from 2025-12-01 21-31-11.png | 327.67 KB | catch |
Issue fork drupal-3560920
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:
- 3560920-move-gitlabci.yml-jobs
changes, plain diff MR !14013
Comments
Comment #3
catchComment #4
mondrakeno brainer
Comment #5
catchWe could potentially move the phpunit jobs before the lint jobs since they're generally faster, I don't know if that's doable with the same visual representation though. But also, can just see how this goes.
Comment #6
catchYou can see the ~5s spread between job start times in the 'jobs' summary.
Comment #7
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #9
catchTried some things with Functional js tests but there is some kind of fundamental constraint that splitting into more jobs and lower or higher concurrency does not help with.
The original idea of moving unit tests after lint job does help all the main test jobs start earlier still. Got at least two sub-5 minute test runs on the MR which is not very common.
Comment #10
catchComment #11
smustgrave commentedlets do it! No objections.
Comment #12
quietone commentedYes, let's do this one. I read the comments, mr and updated credit.
Comment #13
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #14
catchRebased.
Comment #16
godotislateCommitted fdd25a7 and pushed to main. Thanks!
Change did not apply to 11.x, so setting to Fixed unless someone wants to reopen with a backport.