-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
chore: add build-args for git-commit etc #14114
chore: add build-args for git-commit etc #14114
Conversation
Add the ability to specify `GIT_TAG`, `GIT_COMMIT`, `BUILD_DATE` and `GIT_TREE_STATE` as optional build-args. As well as resolving argoproj#13683 (which was caused by argoproj#12620), this has the bonus of making the `docker build` slightly more deterministic (since we now have the ability to specify the same inputs into the docker build which was hitherto computed on every `docker build`). Signed-off-by: Blake Pettersson <[email protected]>
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #14114 +/- ##
==========================================
+ Coverage 49.56% 49.62% +0.05%
==========================================
Files 256 256
Lines 43920 43925 +5
==========================================
+ Hits 21770 21796 +26
+ Misses 19987 19973 -14
+ Partials 2163 2156 -7 ☔ View full report in Codecov by Sentry. |
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.
After discussing the changes over with Blake via Zoom. I'm in favor of reverting #12620 & #12640.
Although this PR would fix the issue with our images, end users building their own custom images would still be affected. https://argo-cd.readthedocs.io/en/stable/operator-manual/custom_tools/#byoi-build-your-own-image
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.
I like this PR
Co-authored-by: Josh Soref <[email protected]> Signed-off-by: Blake Pettersson <[email protected]>
@34fathombelow lgty? |
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.
LGTM!
@crenshaw-dev Can we cherry-pick this to 2.7?
/cherry-pick release-2.7 |
Cherry-pick failed with |
Thanks guys! |
* build: add build-args for git-commit etc Add the ability to specify `GIT_TAG`, `GIT_COMMIT`, `BUILD_DATE` and `GIT_TREE_STATE` as optional build-args. As well as resolving argoproj#13683 (which was caused by argoproj#12620), this has the bonus of making the `docker build` slightly more deterministic (since we now have the ability to specify the same inputs into the docker build which was hitherto computed on every `docker build`). Signed-off-by: Blake Pettersson <[email protected]> * Update .github/workflows/image-reuse.yaml Co-authored-by: Josh Soref <[email protected]> Signed-off-by: Blake Pettersson <[email protected]> --------- Signed-off-by: Blake Pettersson <[email protected]> Co-authored-by: Josh Soref <[email protected]>
* build: add build-args for git-commit etc Add the ability to specify `GIT_TAG`, `GIT_COMMIT`, `BUILD_DATE` and `GIT_TREE_STATE` as optional build-args. As well as resolving argoproj#13683 (which was caused by argoproj#12620), this has the bonus of making the `docker build` slightly more deterministic (since we now have the ability to specify the same inputs into the docker build which was hitherto computed on every `docker build`). Signed-off-by: Blake Pettersson <[email protected]> * Update .github/workflows/image-reuse.yaml Co-authored-by: Josh Soref <[email protected]> Signed-off-by: Blake Pettersson <[email protected]> --------- Signed-off-by: Blake Pettersson <[email protected]> Co-authored-by: Josh Soref <[email protected]>
Add the ability to specify
GIT_TAG
,GIT_COMMIT
,BUILD_DATE
andGIT_TREE_STATE
as optional build-args. As well as resolving #13683 (which was caused by #12620), this has the bonus of making thedocker build
slightly more deterministic (since we now have the ability to specify the same inputs into the docker build which was hitherto computed on everydocker build
).Note on DCO:
If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.
Checklist:
Please see Contribution FAQs if you have questions about your pull-request.