You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: