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

cmd/go: semver versioning of tools used in the build #28512

Closed
KantarBruceAdams opened this issue Oct 31, 2018 · 2 comments

Comments

Projects
None yet
2 participants
@KantarBruceAdams
Copy link

commented Oct 31, 2018

Modules solves the versioning issue for dependencies that are packages

There does not seem to be a solution for tools used in the build process.
For example if I create build scripts that use go2xunit I must still use go get to install it.
If a new version of those projects is released it could break my build if "go get" is part of the build script.
If it is not part of the build script then it must be part of the build environment which makes builds environmentally sensitive. This defers but does not eliminate the problem. My build might not be reproducible if I set up a new environment in the future (using go get at that point).

@KantarBruceAdams

This comment has been minimized.

Copy link
Author

commented Oct 31, 2018

Also raised on stack overflow though that is seeking a practical solution for an earlier version of go. This ticket is for go itself.

@myitcv

This comment has been minimized.

Copy link
Member

commented Oct 31, 2018

Dup of #25922 and #27653

@myitcv myitcv closed this Oct 31, 2018

@myitcv myitcv added the modules label Oct 31, 2018

@myitcv myitcv changed the title semver versioning of tools used in the build cmd/go: semver versioning of tools used in the build Oct 31, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.