-
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
Run "go mod vendor" in verify-gomod #9389
Conversation
This will actually catch vendoring issues
Skipping CI for Draft Pull Request. |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet 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 |
/test pull-kops-verify-gomod |
Whoops! Thanks for catching this mistake I made :-) I know it's WIP, but looks good so far! |
It looks like go is still downloading the modules into the mod cache rather than using the vendor directory. I'm sure theres an env var that we can set in the Makefile to tell go to use the vendor directory every time, and that this default behavior changed between 1.13 and 1.14. k/k is still on 1.13 but is hoping to upgrade to 1.14 for k8s 1.19, so maybe we just follow suit once that lands and our jobs should start using the vendor directory automatically. regardless, that can be in a followup PR |
/test pull-kops-verify-gomod |
/lgtm |
Thanks @rifelpet . I believe the flag is |
…89-upstream-release-1.18 Automated cherry pick of #9389: Run "go mod vendor" in verify-gomod
This will actually catch vendoring issues.
also removing it from
make travis-ci
becausemake gomod
depends on bazel which isnt available in travis.make gomod
has its own prow job though, so we still get sufficient coverage.