Skip to content
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

EVG-15628: use Go modules #243

Merged
merged 4 commits into from
Nov 1, 2021
Merged

EVG-15628: use Go modules #243

merged 4 commits into from
Nov 1, 2021

Conversation

Kimchelly
Copy link
Contributor

@Kimchelly Kimchelly commented Oct 27, 2021

Jira:
https://jira.mongodb.org/browse/EVG-15628

I don't think Evergreen will be able to test this PR because it's such a large diff. I tried testing out most of the targets locally and they succeeded.

  • Use Go modules and remove vendored dependencies. Instead, the dependencies for our repositories will be dynamically fetched during runtime using go mod tidy.
  • Upgrade dependencies to the newest minor version. This is somewhat risky since we have outdated dependencies, but I would prefer to take the pain of upgrading them as much as possible now since we'll eventually have to upgrade our dependencies anyways. I'm going to assume that repos are obeying semantic versioning, so minor version upgrades are supposed to be backwards compatible.
  • Update README for modules instead of vendoring.
  • Update and standardize the Evergreen YAML file. The GOMODCACHE is set because for CI tests, it's better to not write outside of the agent working directory for Evergreen since it won't clean it up.

@Kimchelly Kimchelly changed the title EVG-15446, EVG-15628: use Go modules EVG-15628: use Go modules Oct 27, 2021
@Kimchelly Kimchelly merged commit 2b42087 into mongodb:main Nov 1, 2021
@Kimchelly Kimchelly deleted the EVG-15628_adopt_modules branch November 1, 2021 16:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants