-
Notifications
You must be signed in to change notification settings - Fork 113
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
oasis-node binaries made with GoReleaser via GitHub Actions are not reproducible #2571
Comments
|
Wasn't that included in latest Go (e.g., 1.13.6)? |
As far as I can tell the only differences in the binary are:
|
It turned out this is a specific issue when performing builds via GoReleaser and using different git paths. Filled https://github.com/oasislabs/goreleaser/issues/1 and implemented a work-around in #2590. |
tjanez
changed the title
oasis-node builds are not reproducible
oasis-node binaries made with GoReleaser via GitHub Actions are not reproducible
Jan 23, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
SUMMARY
When testing the release tooling I noticed that
oasis-node
builds are not reproducible, i.e. rebuilding the same git tag checkout does not produce the sameoasis-node
binary.ISSUE TYPE
OS / ENVIRONMENT
Go 1.13 on Ubuntu 18.04 LTS as provided by GitHub Actions.
ACTUAL RESULTS
EXPECTED RESULTS
Sha256sum of the rebuild of
oasis-node
from the same source tree should be equal to the released version.The text was updated successfully, but these errors were encountered: