Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix(ci): only run jobs when their ancestors on prevoius stages succee…
…ded (#5412) ## Issue being fixed or feature implemented We should not be running jobs if their ancestors failed. This was broken with the introduction of `FAST_MODE`/`.skip-in-fast-mode-template` I think (via #3635). ## What was done? Adjust ci rules, make them explicit. ## How Has This Been Tested? Compare `test` stages: https://gitlab.com/dashpay/dash/-/pipelines/888510672 (note: some of `test` stage jobs were started, even though all related jobs from `build` stage have failed) vs https://gitlab.com/UdjinM6/dash/-/pipelines/888923382 (note: none of `test` stage jobs were started) ## Breaking Changes n/a ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
- Loading branch information