Hi folks,
The Bitcoin Core developers have a desire to do a mostly bug-fix, cleanup and translation update release in v0.9.2 a few weeks from now. You do not need to be a developer to help! With these unofficial nightly builds, power users can more easily aid in testing of the master branch which will help to find bugs and polish things up faster. Additionally translators can more easily run the latest code and see what strings need to be translated as we rapidly approach the next stable release.
WARNING: Nightly builds are potentially dangerous. These builds are untested and may contain bugs. While every effort is taken to maintain security of the build and web server, we are not responsible for anything that goes wrong. It is up to the user to protect their own data, and to the community to use Gitian to independently make matching builds and to point out if something has gone horribly wrong.Unofficial Nightly Buildshttp://nightly.bitcoin.itBuilds will appear here roughly once a day. Sometimes there will be no new build if nothing changed in master.
(This has nothing to do with the wiki. They just provided a convenient subdomain and Cloudflare protection of the download server.)
Source and Binary Reproducibilityhttps://github.com/nightlybitcoin/bitcoin/brancheshttps://github.com/nightlybitcoin/bitcoin/releaseshttps://github.com/nightlybitcoin/gitian.sigsAll binary builds are byte-for-byte reproducible by using Gitian to build a particular tag in git. For example, the
0.9.99.0-20140415-74dd52a branch denotes in a custom version tag
v0.9.99.0-20140415-74dd52a with build date of
20140415 and the
74dd52a commit from master. Sometimes the nightly build will contain PR's. This particular tag includes PR 4042 and PR 4049 that are both important for the next release.
Bug Reportinghttps://github.com/bitcoin/bitcoin/issuesIf you run into any problem with these builds please search the Bitcoin Github issues to find if it is already a known problem. If your issue is not yet reported, file a new ticket and explain the problem. You should include the exact name of the build you are using (i.e.
v0.9.99.0-20140415-74dd52a) so the developers know exactly what you are talking about. It would be helpful if you include a link to the branch used to build it which can be obtained from the
README-SOURCE within the Linux tarball or Windows download directory. For example, a typical branch will look something like
this. Include that link in your issue ticket and it will save time of the developers.
TODO's ... any Volunteers?* There are many things that can be done to improve these automated nightly builds. One of the most important has to do with security of the binaries. Since each build is byte-for-byte reproducible from each git tag with Gitian, it should be possible for two or more independent builders to validate the results in an automated fashion. Anyone interested in doing this?
Builder Changelog2014-05-21: MacOS X builds added.
2014-05-13: Separate builds for master and 0.9.2 branch.
2014-04-16: Add auto-commit to gitian.sigs.
2014-04-15: Add GPG signatures to git tag.
2014-04-15: Deployed.
2014-04-13: Implemented nightly auto builder.