-
Notifications
You must be signed in to change notification settings - Fork 454
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
[ci] build + release with go1.12 (again) #1674
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1674 +/- ##
========================================
+ Coverage 71.8% 71.9% +<.1%
========================================
Files 968 974 +6
Lines 81169 81215 +46
========================================
+ Hits 58345 58403 +58
+ Misses 18990 18978 -12
Partials 3834 3834
Continue to review full report at Codecov.
|
@@ -46,7 +46,7 @@ steps: | |||
command: make clean install-vendor docker-integration-test | |||
env: | |||
CGO_ENABLED: 0 | |||
GIMME_GO_VERSION: 1.10.x | |||
GIMME_GO_VERSION: 1.12.x |
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.
Curious: is there any reason for keeping make clean install-vendor docs-test
on 1.10?
docker-compose.yml
Outdated
@@ -1,5 +1,5 @@ | |||
app: | |||
image: golang:1.10.4-stretch | |||
image: golang:1.12.1-stretch |
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.
Nitpick: this will run on 1.12.1
, while Buildkite (as well as Dockerfile below) will give you 1.12.5
once it expands 1.12.x
.
b185185
to
87c95da
Compare
Thanks for the heads up @bai! |
87c95da
to
36ab7df
Compare
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
To be merged after ongoing docker fixes.
What this PR does / why we need it:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing and/or backwards incompatible change?:
Does this PR require updating code package or user-facing documentation?: