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

Improve release process to handle multiple tags on same commit #420

Open
kumaritanushree opened this issue Jun 27, 2023 · 0 comments
Open
Assignees
Labels
bug This issue describes a defect or unexpected behavior carvel-accepted This issue should be considered for future work and that the triage process has been completed

Comments

@kumaritanushree
Copy link
Contributor

What steps did you take:
Triggered a tag t1 on commit x and for some reason release action did not pass.
Triggered a new tag t2 on commit x and now release action passed and uploaded artefacts in draft release, but these artifacts have wrong info like tag. It is publishing file like release.yaml and package.yaml with tag t1 instead of t2.

What happened:
[A small description of the issue]

What did you expect:
It should always pick latest tag that is t2

Anything else you would like to add:
[Additional information that will assist in solving the issue.]

Environment:

  • secretgen-controller version (execute kubectl get deployment -n secretgen-controller secretgen-controller -o yaml and the annotation is kbld.k14s.io/images):
  • Kubernetes version (use kubectl version)

Vote on this request

This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.

👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"

We are also happy to receive and review Pull Requests if you want to help working on this issue.

@kumaritanushree kumaritanushree added bug This issue describes a defect or unexpected behavior carvel-triage This issue has not yet been reviewed for validity labels Jun 27, 2023
@kumaritanushree kumaritanushree self-assigned this Jun 27, 2023
@renuy renuy added carvel-accepted This issue should be considered for future work and that the triage process has been completed and removed carvel-triage This issue has not yet been reviewed for validity labels Jul 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This issue describes a defect or unexpected behavior carvel-accepted This issue should be considered for future work and that the triage process has been completed
Projects
Status: Prioritized Backlog
Development

No branches or pull requests

2 participants