While working on #3460760: CI: improve UI-related CI jobs:`UI eslint` obscures TypeScript Compiler errors, `npm run build` runs too late, I was reminded of what I observed a few weeks ago: that changes exclusively in the ui/ directory still run all the back-end-only CI jobs, such as phpcs, phpstan and phpunit.
(Well, phpunit is affected also by changes to the components directory, since it tests the PHP logic finding matches for each component prop — but SDCs themselves are running on the back-end too. Easy enough to take into account.)
None. Faster CI runs for UI-only changes.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | Screenshot 2024-07-11 at 1.02.09 PM.png | 294.69 KB | wim leers |
Show commandsStart 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:
changes
Comments
Comment #3
wim leersThis MR touches only
.gitlab-ci.yml, and so there's no point in running most CI jobs … which now actually is the case:🥳🚀
Comment #4
wim leersComment #6
wim leersThis caused a regression. CI jobs are not running when they should:
😭
Comment #7
wim leersI've read and re-read https://docs.gitlab.com/ee/ci/yaml/#rulesif and I can't make sense of why it's not working. Attempted fix on another issue/MR failed: https://git.drupalcode.org/project/experience_builder/-/merge_requests/6...
Comment #10
wim leers