-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Switch to golang 1.11.5 #6798
Switch to golang 1.11.5 #6798
Conversation
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: justinsb The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@justinsb we’ll need to remove the 1.10 tests and run gofmt against the existing code base to deal with the formatting changes that were introduced in 1.11 |
Using the approach from k8s.io/repo-infra. This avoids problems where we are testing with a different version of go than we are building with.
So that we can source the correct version of go & gofmt, it makes sense to use the gofmt from the bazel @go_sdk, as done in k8s.io/repo-infra. This requires that we use the bazel image. Related PR kubernetes/kops#6798
/test pull-kops-verify-gofmt |
So that we can source the correct version of go & gofmt, it makes sense to use the gofmt from the bazel go_sdk, as done in k8s.io/repo-infra. This requires that we use the bazel image. Related PR kubernetes/kops#6798
Working on fixing the gofmt test job, it's currently locked on a particular go version: kubernetes/test-infra#12298 |
pull-kops-verify-gofmt job change was merged upstream, so... /retest |
This lets us exclude the gofmt task which now requires bazel and also now runs in a separate test. Continuing with this should allow us to have a faster travis-ci, that should also give us better coverage (we really want travis to test osx & windows builds)
Just food for thought, would it be more maintainable to install Bazel in the Travis image using before_install like in https://github.com/bazelbuild/rules_go/blob/master/.travis.yml instead of having a separate CI test for it instead? |
@rdrgmnzs I did think about it, but it's pretty slow to download bazel every time, and I think generally I'd rather move testing out of travis, and into prow. I imagine we end up with travis primarily testing that kops itself builds on osx & linux (& windows?), on multiple go versions. That's much harder to do in prow. |
Makes sense, thanks @justinsb ! /lgtm |
Cherry pick of #6798 onto release-1.13
For cherry-picking to 1.13
https://github.com/kubernetes/kubernetes/blob/release-1.13/build/build-image/cross/Dockerfile