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

[TEP-0133] Apply default resolver to finally tasks #6481

Conversation

QuanZhang-William
Copy link
Member

@QuanZhang-William QuanZhang-William commented Mar 31, 2023

Changes

Fixes #6449. Prior to this commit, the default resolver is only applied to PipelineTasks but not finally PipelineTasks.

This commit applies the default resolver to the finally PipelineTasks in the same way as normal PipelineTasks. This commit also refactors the common code to a PipelineTask SetDefaults function.

/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

TEP-0133: Apply default resolver to finally tasks

Fixes tektoncd#6449. Prior to this commit, the default resolver is only applied to PipelineTasks but not finally PipelineTasks.
This commit applies the default resolver to the finally PipelineTasks in the same way as normal PipelineTasks.
This commit also refactors the common code to a PipelineTask SetDefaults function.

/kind bug

[tektoncd#6449]: tektoncd#6449
@tekton-robot
Copy link
Collaborator

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@tekton-robot tekton-robot added release-note-none Denotes a PR that doesnt merit a release note. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. kind/bug Categorizes issue or PR as related to a bug. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Mar 31, 2023
@tekton-robot tekton-robot added release-note Denotes a PR that will be considered when it comes time to generate release notes. and removed release-note-none Denotes a PR that doesnt merit a release note. labels Mar 31, 2023
@QuanZhang-William
Copy link
Member Author

/test all

@QuanZhang-William QuanZhang-William marked this pull request as ready for review April 3, 2023 15:18
@jerop jerop removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 5, 2023
@jerop jerop self-assigned this Apr 5, 2023
@jerop
Copy link
Member

jerop commented Apr 5, 2023

/assign @chitrangpatel

Copy link
Member

@wlynch wlynch 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 Apr 5, 2023
@lbernick lbernick added this to the Pipelines v0.47 milestone Apr 6, 2023
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lbernick

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 6, 2023
@tekton-robot tekton-robot merged commit a91cff0 into tektoncd:main Apr 6, 2023
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/XL Denotes a PR that changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Default Resolver is not set for Finally Tasks
6 participants