Add explicit ARG ARO_VERSION
to RP build stage in ci-rp
#3597
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue this PR addresses:
Fixes no Jira
What this PR does / why we need it:
The
go-toolset
image used to build the ARO binary inmake ci-rp
sets its ownVERSION
environment variable, overriding theVERSION
arg we pass in. This results in theversion.GitCommit
ldflag being set to an incorrect value (version of Go in the go-toolset image).This PR changes the name of this argument to
ARO_VERSION
to avoid this naming conflict, and additionally explicitly sets this arg on the RP build stage, since all ARGs are set to nil at the completion of each stage in a multi-stage build.Test plan for issue:
make ci-rp
with this change in place, and ensured the resulting binary has the correct ldflags set forversion.GitCommit
.Is there any documentation that needs to be updated for this PR?
No
How do you know this will function as expected in production?
N/A (output of
make ci-rp
not yet used in production)