Fix Jenkins build failure #128
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
subpop
force-pushed
the
random-try-to-make-build
branch
3 times, most recently
from
ebe090b
to
8b0ac81
Compare
subpop
force-pushed
the
random-try-to-make-build
branch
from
8b0ac81
to
69ac649
Compare
subpop
force-pushed
the
random-try-to-make-build
branch
from
69ac649
to
99a67c0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Go 1.18+ looks to embed VCS information into the binary when compiling. https://go.dev/doc/go1.18#go-version. The build version of Go needs to get pinned to 1.17 in order to avoid the build failure. Eventually, we can update the Dockerfile so that VCS metadata (
.git) gets copied into the build container too.