Skip to content
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

Apply replacements to workspace subpath for finally tasks #5572

Merged

Conversation

abayer
Copy link
Contributor

@abayer abayer commented Sep 28, 2022

Changes

Fixes #5571

When #4351 was done, it didn't do workspace subpath replacement for finally tasks as well. This corrects that.

Note - propagateParams also isn't called for finally tasks, but I'm not sure if that's by design, so I left it as is.

/kind bug

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

  • Has Docs included if any changes are user facing
  • Has Tests included if any functionality added or changed
  • Follows the commit message standard
  • Meets the Tekton contributor standards (including
    functionality, content, code)
  • Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
  • Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
  • Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

Variable replacement is now properly performed for workspace sub-paths in finally tasks.

Fixes tektoncd#5571

When tektoncd#4351 was done, it didn't do workspace subpath replacement for `finally` tasks as well. This corrects that.

Note - `propagateParams` also isn't called for `finally` tasks, but I'm not sure if that's by design, so I left it as is.

Signed-off-by: Andrew Bayer <[email protected]>
@abayer abayer added the kind/bug Categorizes issue or PR as related to a bug. label Sep 28, 2022
@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Sep 28, 2022
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Sep 28, 2022
@tekton-robot
Copy link
Collaborator

The following is the coverage report on the affected files.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/reconciler/pipelinerun/resources/apply.go 97.3% 97.3% 0.0

@abayer
Copy link
Contributor Author

abayer commented Sep 28, 2022

/retest

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 28, 2022
@abayer
Copy link
Contributor Author

abayer commented Sep 28, 2022

/retest

Copy link
Member

@jerop jerop left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 4, 2022
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerop, vdemeester

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jerop
Copy link
Member

jerop commented Oct 4, 2022

Note - propagateParams also isn't called for finally tasks, but I'm not sure if that's by design, so I left it as is.

@abayer thanks for noting this - this was not by design, @chitrangpatel opened #5588 which is fixed in #5593

@tekton-robot tekton-robot merged commit f551682 into tektoncd:main Oct 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. release-note Denotes a PR that will be considered when it comes time to generate release notes. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Replacements not applied to finally task workspaces
4 participants