Reorder and cleanup rules for assets jobs
What does this MR do and why?
Reorder and cleanup rules for assets jobs
Namely for compile-production-assets
and build-assets-image
.
- Some rules from
build-assets-image
are removed because it depends oncompile-production-assets
and they don't present there. It means even if it matches, it'll be invalid because the needed job doesn't exist anyway. - Reordering the rules so it's easier to stop them from running when the merge request is not approved. This is not done yet because there are other dependant jobs (E2E jobs) that we need to walk through before making this happen.
This merge request is aiming to make the iterative merge requests easier to review, by merging the standalone prerequisite changes first.
No actual behaviour changes expected.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Screenshots or screen recordings
Screenshots are required for UI changes, and strongly recommended for all other merge requests.
Before | After |
---|---|
How to set up and validate locally
Numbered steps to set up and validate the change are strongly suggested.
Related to #449031 (closed)