-
Notifications
You must be signed in to change notification settings - Fork 18
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
Show git commit in porchctl version
#103
Conversation
I think adding the git commit is very useful. But maybe we could also set the This change will do it:
Here, we are using the current date to set the PORCHCTL_VERSION env var but we could set that using some more official method. The line Line 160 in 114895d
You can examine the contants in the built porchctl binary just like in Then you build porchctl and set the value of the global constant at link time as follows:
|
thanks @liamfallon, it is a good idea to set the version not just during the release process, but also on every build. I've modified the Makefile as you suggested. |
I was looking for this yesterday, you solved my puzzlement as to how the version was set during the release! |
/approve |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to merge this so we can figure out if the correct Porch version is being used in the failing e2e tests.
/approve
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: efiacor, kispaljr, liamfallon 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 |
/retest |
2 similar comments
/retest |
/retest |
No description provided.