cherry-pick to 0.27.x: Propagate Pipeline name label to PipelineRun #4174
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Cherry-pick #4163 into v0.27.x branch in preparation for a v0.27.2 release on Monday.
The above fixes a bug where Pipelines created in Pending or Cancelled state wouldn't receive a
tekton.dev/pipeline = <pipelineName>
label, limiting the ability to filter for them.Another commit was added to resolve a small skew in some publicly exported constants that have changed on
main
after the v0.27 branch was cut. Bringing the updated label constants over to 0.27 would be, I think, technically a breaking change - if someone were importing pipelines @ 0.27 into their codebase they'd need to update usage of these constants in their own code from one patch release to the next. 🤷 I don't know how likely this really is but I figure it doesn't hurt./kind misc
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes