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

[release-v0.43.x] ChildReference status helper functions should support both CustomRuns and Runs #5941

Conversation

tekton-robot
Copy link
Collaborator

This is an automated cherry-pick of #5936

/assign vdemeester

Status helper functions now properly support both CustomRuns and Runs.

… and Runs

fixes tektoncd#5933

I updated `pkg/status` to support `CustomRun`s early in the work for supporting `CustomRun`s in the `PipelineRun` reconciler, but forgot to add back support for `Run`s as well when we moved to the reconciler supporting both, depending on a feature flag. This broke tektoncd/cli#1838. This change brings back support for `Run`s in the status helper functions, alongside the support for `CustomRun`s.

Signed-off-by: Andrew Bayer <[email protected]>
@tekton-robot tekton-robot added the release-note Denotes a PR that will be considered when it comes time to generate release notes. label Jan 4, 2023
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Jan 4, 2023
@vdemeester
Copy link
Member

/kind bug
/approve
/cc @abayer @pritidesai @jerop

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label Jan 4, 2023
@tekton-robot
Copy link
Collaborator Author

[APPROVALNOTIFIER] This PR is APPROVED

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

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 4, 2023
@abayer
Copy link
Contributor

abayer commented Jan 4, 2023

The pull-tekton-pipeline-build-tests failure is due to the updates to golangci-lint in tektoncd/plumbing#1308 (picked up in the Prow jobs in tektoncd/plumbing#1309), which is going to be a problem for backport builds in general...

abayer added a commit to abayer/tektoncd-pipeline that referenced this pull request Jan 4, 2023
We hit an issue on tektoncd#5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
abayer added a commit to abayer/tektoncd-pipeline that referenced this pull request Jan 4, 2023
We hit an issue on tektoncd#5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
abayer added a commit to abayer/tektoncd-pipeline that referenced this pull request Jan 4, 2023
We hit an issue on tektoncd#5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit that referenced this pull request Jan 4, 2023
We hit an issue on #5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit to tekton-robot/pipeline that referenced this pull request Jan 4, 2023
We hit an issue on tektoncd#5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit to tekton-robot/pipeline that referenced this pull request Jan 4, 2023
We hit an issue on tektoncd#5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit to tekton-robot/pipeline that referenced this pull request Jan 4, 2023
We hit an issue on tektoncd#5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit to tekton-robot/pipeline that referenced this pull request Jan 4, 2023
We hit an issue on tektoncd#5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit that referenced this pull request Jan 4, 2023
We hit an issue on #5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit that referenced this pull request Jan 4, 2023
We hit an issue on #5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit that referenced this pull request Jan 5, 2023
We hit an issue on #5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
tekton-robot pushed a commit that referenced this pull request Jan 5, 2023
We hit an issue on #5941 due to the golangci-lint installed on the `test-runner` image being upgraded and reporting new issues that weren't encountered at the time of the v0.43.0 release. Ideally, the build tests job should be using the same golangci-lint version as is defined in the Makefile, so let's switch to calling a make target.

Signed-off-by: Andrew Bayer <[email protected]>
@abayer
Copy link
Contributor

abayer commented Jan 5, 2023

/retest

@lbernick
Copy link
Member

lbernick commented Jan 5, 2023

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jan 5, 2023
@abayer
Copy link
Contributor

abayer commented Jan 5, 2023

/retest

@tekton-robot tekton-robot merged commit a1bac54 into tektoncd:release-v0.43.x Jan 5, 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/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants