-
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
Propagated Parameters for Finally Tasks #5593
Propagated Parameters for Finally Tasks #5593
Conversation
The following is the coverage report on the affected files.
|
/kind feature |
9604904
to
35615de
Compare
The following is the coverage report on the affected files.
|
/test pull-tekton-pipeline-unit-tests |
@chitrangpatel: 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 tekton-pipeline-unit-tests |
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks for the quick fix @chitrangpatel!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Propagated parameters was only called for regular pipeline tasks, not finally tasks. This was due to an oversight, and not a design choice. This PR extends the propagated paramsters usage to finally tasks now. It addresses issue tektoncd#5588 .
35615de
to
e64918a
Compare
The following is the coverage report on the affected files.
|
/lgtm |
/retest |
Changes
Propagated parameters was only called for regular pipeline tasks, not finally tasks. This was due to an oversight, and not a design choice. This PR extends the propagated paramsters usage to finally tasks now. It addresses issue #5588 .
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes