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

Re-add tekton.dev/task label to taskruns from ClusterTasks #2456

Merged
merged 1 commit into from Apr 21, 2020
Merged

Re-add tekton.dev/task label to taskruns from ClusterTasks #2456

merged 1 commit into from Apr 21, 2020

Conversation

ghost
Copy link

@ghost ghost commented Apr 21, 2020

Changes

In #2390 TaskRuns referencing ClusterTasks had their label changed from tekton.dev/task=<Name> to tekton.dev/clusterTask=<Name>. This is a backwards-incompatible change for teams relying on that original taskrun label. In an API Working Group call yesterday there was general agreement that we should cover these labels as part of Tekton Pipeline's API Compatibility Policy.

This commit adds both labels to TaskRuns referencing ClusterTasks. We can then deprecate the tekton.dev/task= label on these TaskRuns in line with the API Compatibility Policy.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Double check this list of stuff that's easy to miss:

Reviewer Notes

If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.

Release Notes

Keep tekton.dev/task label in addition to tekton.dev/clusterTask on taskruns of clustertask for backwards compatibility.

In #2390 TaskRuns referencing ClusterTasks had their label changed
from tekton.dev/task=<Name> to tekton.dev/clusterTask=<Name>. This
is a backwards-incompatible change for teams relying on that original
task label.

This commit adds both labels to TaskRuns referencing ClusterTasks.
We can then deprecate the tekton.dev/task= label on these TaskRuns
in accordance with Pipelines' API deprecation policy.
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Apr 21, 2020

CLA Check
The committers are authorized under a signed CLA.

@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Apr 21, 2020
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Apr 21, 2020
Copy link
Member

@vdemeester vdemeester 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 lgtm Indicates that a PR is ready to be merged. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Apr 21, 2020
Copy link
Member

@danielhelfand danielhelfand 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
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: danielhelfand, 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

@ghost
Copy link
Author

ghost commented Apr 21, 2020

/test pull-tekton-pipeline-integration-tests

@tekton-robot tekton-robot merged commit a68d753 into tektoncd:master Apr 21, 2020
@afrittoli afrittoli added the kind/bug Categorizes issue or PR as related to a bug. label Apr 30, 2020
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. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants