Collapse -success and -failure jobs into an -outcome job
#124014
Conversation
Before this commit we had auto-success, auto-failure, try-success and try-failure. The only difference between a -success and a -failure job though was the exit code that was returned in the job. To reduce clutter, this PR collapses each pair of jobs into a single job that is executed regardless of whether the dependency jobs passed or failed. Then a simple jq invocation checks whether the dependencies passed or failed to determine the exit code.
|
Could not assign reviewer from: |
|
@pietroalbini: no appropriate reviewer found, use |
rustbot
added
A-testsuite
|
Please choose another assignee. (see documentation) |
|
r? @Kobzol |
| # These snippets are used by the try-success, try-failure, auto-success and auto-failure jobs. | ||
| # Check out their documentation for more information on why they're needed. | ||
|
|
||
| - &base-outcome-job |
There was a problem hiding this comment.
The comment above this isn't updated (it still mentions try-success etc.)
| <<: *base-success-job | ||
| auto-failure: | ||
| # !cancelled() executes the job regardless of whether it passed or failed | ||
| if: "!cancelled() && github.event_name == 'push' && (github.ref == 'refs/heads/try' || github.ref == 'refs/heads/try-perf') && github.repository == 'rust-lang-ci/rust'" |
There was a problem hiding this comment.
Just thinking out loud: do we actually need this if (more specifically, the github.XXX parts? Shouldn't this job be skipped automatically if try (which it needs) is skipped?
|
@rustbot author |
rustbot
added
S-waiting-on-author
|
☔ The latest upstream changes (presumably #124175) made this pull request unmergeable. Please resolve the merge conflicts. |
|
Superseded by #124366. |
4 participants
Before this commit we had
auto-success,auto-failure,try-successandtry-failure. The only difference between a-successand a-failurejob though was the exit code that was returned in the job.To reduce clutter, this PR collapses each pair of jobs into a single job that is executed regardless of whether the dependency jobs passed or failed. Then a simple jq invocation checks whether the dependencies passed or failed to determine the exit code.
r? @Kobzol