-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Run finally pipeline even if task is failed at the validation #8314
base: main
Are you sure you want to change the base?
Conversation
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/kind bug |
/test check-pr-has-kind-label |
@divyansh42: The specified target(s) for
The following commands are available to trigger optional jobs:
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/test pull-tekton-pipeline-go-coverage-df |
@divyansh42: The specified target(s) for
The following commands are available to trigger optional jobs:
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
57012ed
to
9cb5f91
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
9cb5f91
to
5265441
Compare
/hold cancel |
/cc @vdemeester @afrittoli @chitrangpatel |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
Presently if one of the task in pipeline is consuming result from the previous task but the previous failed to produce the result then pipeline fails without running the finally tasks. These changes handles tasks which got failed in the validation step. Signed-off-by: divyansh42 <diagrawa@redhat.com>
5265441
to
ceb2f6c
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-go-coverage |
@afrittoli, I have made the changes as per the discussion above. |
/test pull-tekton-pipeline-unit-tests |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/retest-required |
1 similar comment
/retest-required |
/test pull-tekton-pipeline-go-coverage |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-unit-tests |
/test pull-tekton-pipeline-go-coverage-df |
@divyansh42: The specified target(s) for
The following commands are available to trigger optional jobs:
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-unit-tests |
1 similar comment
/test pull-tekton-pipeline-unit-tests |
Signed-off-by divyansh42 <diagrawa@redhat.com>
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-alpha-integration-tests |
Signed-off-by: divyansh42 <diagrawa@redhat.com>
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-beta-integration-tests |
/test pull-tekton-pipeline-go-coverage-df |
@afrittoli: The specified target(s) for
The following commands are available to trigger optional jobs:
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
The following is the coverage report on the affected files.
|
@afrittoli, I have made the changes as per the discussion that happened over the Slack channel. Could you please take a look again? |
Fixes: #7330
Changes
Presently if one of the tasks in the pipeline is consuming results from the previous task but the previous task failed to produce the result then the pipeline fails without running the
finally
tasks.These changes handle tasks that failed in the validation step by adding it to the new field named
ValidationFailedTasks
under structPipelineRunFacts
which will have all the tasks for which the taskrun is not created as it failed in the validation step by the controller.These changes will also remove the logic of panic errors occurring if any of the validation fails. Instead of the controller returning a permanent error, it will remove all the tasks that have to be scheduled. This also changes the skip logic to skip the task and stop running the pipeline if any of the validation is failed.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes