der-eismann
commented
1 year ago Okay, just to keep this going, executing a git status in the container build gives this output:
git status output
``` HEAD detached at v2.7.3 Changes not staged for commit: (use "git add/rmI'm pretty sure #12620 caused this, as the whole issue disappears when I revert c6f32e5b0823fd08ec905198ae75efe247b4d2c6. Also it doesn't bring any improvement regarding image size since in the last step only the binaries are copied to the final image, nothing else. It might improve local development speed, but this is not a very good solution then. I would propose to revert #12620, do you have an opinion on that @blakepettersson?
blakepettersson
crenshaw-dev
jesserhodes-expel
rufreakde
MaliFotouhi
Checklist:
argocd version.Describe the bug
After upgrading from ArgoCD 2.6.7 to 2.7.2, the UI and CLI are reporting the version as
v2.7.2+cbee7e6.dirty. This is probably just a small error during the CI process, but could also mean that the contents of the Git repository were modified during the build process. This started happening with 2.7.0, 2.6.7 was still fine.To Reproduce
Just start the
quay.io/argoproj/argocd:v2.7.2container image and executeargocd version.Expected behavior
Version should be reported as
v2.7.2+cbee7e6without thedirtytag.Screenshots
Version
Logs
Should be irrelevant