Add way to distinguish success and success-with-errors for continue-on-error jobs
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 6.3k
- Forks
- 1.4k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 24
Description
Describe the enhancement
I have a few jobs that I don't want to fail the workflow on failure. However, I do want to be able to react to the failure in further jobs, i.e. with needs.A.result. This is currently impossible: continue-on-error means that even if the job errors, the result is set to success (note that the UI still shows failure).
I would like for either result to be set to failed or a new state (errored?) when a continue-on-error job errors, or for there to be some other way to detect errors in continue-on-error jobs. The best solution is probably what is currently done for steps: a pre-continue-on-error output (e.g. outcome) and a post one (e.g. conclusion, but could keep the name result)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how the runner handles continue-on-error for jobs and how it produces needs.A.result. Compare that behavior with the steps context's outcome and conclusion described in the linked documentation. Done means downstream jobs can distinguish an actual failure from a successful job without failing the workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100