-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Allow variable substitution in pipeline.tasks[].onError
#8564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I also think this demand is reasonable. |
Hum, I do think this demand is reasonable indeed. I don't see why not implementing it, and I don't think it would have any bad side effect. |
@dmitry-mightydevops and @l-qing - would either of you be interested in contributing the implementation for this? |
I'll give it a try this weekend. /assign |
fix tektoncd#8564 In the reconcile logic of PipelineRun, add the ability to replace the `pipeline.tasks[].onError` field. At the same time, the validation of pipelineSpec legality has been delayed.
fix tektoncd#8564 In the reconcile logic of PipelineRun, add the ability to replace the `pipeline.tasks[].onError` field. At the same time, the validation of pipelineSpec legality has been delayed.
fix tektoncd#8564 In the reconcile logic of PipelineRun, add the ability to replace the `pipeline.tasks[].onError` field. At the same time, the validation of pipelineSpec legality has been delayed.
fix tektoncd#8564 In the reconcile logic of PipelineRun, add the ability to replace the `pipeline.tasks[].onError` field. At the same time, the validation of pipelineSpec legality has been delayed.
fix #8564 In the reconcile logic of PipelineRun, add the ability to replace the `pipeline.tasks[].onError` field. At the same time, the validation of pipelineSpec legality has been delayed.
Feature request
This doc says that only CRD Task accept variable substitution for
spec.steps[].onError
It woulod be nice to support same behavior in
pipeline.tasks[].onError
Use case
So for example I want a flexible control if I need to continue (or stop) the pipeline if tests failed passed via params.
For now It fails with the error:
The text was updated successfully, but these errors were encountered: