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

tekton: do not fail on git status -s #5587

Merged

Conversation

vdemeester
Copy link
Member

@vdemeester vdemeester commented Oct 3, 2022

Changes

It turns out, git status -s fails if the working directory is a "detached" head, which is what happens in our case. This removes that checks as it renders pipeline not releasable at all.

It also "locally" tag it to the specified version so that it will appear in the go build metadata.

Signed-off-by: Vincent Demeester [email protected]
/kind misc
/cc @afrittoli @abayer @imjasonh

Note: I used this to release 0.40.2 already 🙃

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

NONE

It turns out, `git status -s` fails if the working directory is a
"detached" head, which is what happens in our case. This removes that
checks as it renders `pipeline` not releasable at all.

It also "locally" tag it to the specified version so that it will
appear in the go build metadata.

Signed-off-by: Vincent Demeester <[email protected]>
@tekton-robot tekton-robot requested a review from abayer October 3, 2022 14:39
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Oct 3, 2022
@tekton-robot tekton-robot requested a review from afrittoli October 3, 2022 14:39
@tekton-robot tekton-robot added the kind/misc Categorizes issue or PR as a miscellaneuous one. label Oct 3, 2022
@tekton-robot tekton-robot requested a review from imjasonh October 3, 2022 14:39
@tekton-robot tekton-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Oct 3, 2022
Copy link
Member

@imjasonh imjasonh 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 3, 2022
@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abayer

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 Oct 3, 2022
@tekton-robot tekton-robot merged commit 5d34b0c into tektoncd:main Oct 3, 2022
@vdemeester vdemeester deleted the tekton-publish-no-git-status branch October 3, 2022 15:23
@vdemeester
Copy link
Member Author

/cherrypick release-v0.40.x

(Just in case we have to do a 0.40.3 🙃 )

@tekton-robot
Copy link
Collaborator

@vdemeester: new pull request created: #5590

In response to this:

/cherrypick release-v0.40.x

(Just in case we have to do a 0.40.3 🙃 )

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot
Copy link
Collaborator

The following Tekton test failed:

Test name Commit Details Required Rerun command
check-pr-has-kind-label c169e12 link true /test check-pr-has-kind-label

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/misc Categorizes issue or PR as a miscellaneuous one. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. 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.

4 participants