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

wrong git revision number in version output #422

Closed
kadel opened this issue Feb 11, 2017 · 5 comments · Fixed by #423
Closed

wrong git revision number in version output #422

kadel opened this issue Feb 11, 2017 · 5 comments · Fixed by #423
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@kadel
Copy link
Member

kadel commented Feb 11, 2017

code revision from which binary is build is wrong.

▶ make
go build -ldflags="-w -X github.com/kubernetes-incubator/kompose/version.GITCOMMIT=be042c7" -o kompose main.go

▶ ./kompose version
0.2.0 (64433fd)

▶ git rev-parse --short HEAD
be042c7

kompose version should output same revision as current source.
It looks like there is commitid inside version.go Shouldn't this show HEAD as default or something like this?

What if we get rid of this? Do we need to show commit id in version output?

@cdrage
Copy link
Member

cdrage commented Feb 11, 2017

Ahhh.. I changed it to show the Git Commit for the current version instead of HEAD... Should we just get rid of this instead?

@kadel kadel reopened this Feb 13, 2017
@surajssd
Copy link
Member

@kadel you re-opened this? Why is that so?

@kadel
Copy link
Member Author

kadel commented Feb 14, 2017

I hoped that we might discuss here if maybe we wan't to get rid of whole commitid (showing commit id in kompose version output)

@cdrage
Copy link
Member

cdrage commented Jun 26, 2017

@kadel Should we close this? Having the hash in the ID has actually helped in terms of releases as well as troubleshooting (whether or not it's been compiled locally against master, etc.)

@fejta-bot
Copy link

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 30, 2017
@cdrage cdrage closed this as completed Jan 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants