Open s373nZ opened 1 week ago
The build failures appear to be in different place each time, and should not be related to my changes, so I assume they are inherited in CI build failures bubbling up from new changes to master
over the weekend. I'll do my best to monitor the CI and rebase opportunely. Otherwise, please advise.
Some reformatting of the commands and minor syntactical optimizations.
Removed modifications to the CHANGELOG.md
and opted for a Changelog-None
hint in the commit message. Users probably don't care about all the CI processes...
Repro nightly builds
Description
This pull request attempts to address #7117 to implement Github Actions CI/CD to perform nightly reproducible builds. The goal is to catch local file changes that might emerge through the build process and result in a
-modded
release version. Currently supportingfocal
,jammy
andnoble
Ubuntu releases.Have been testing by adding the following to the
on
key of.github/workflows/repro.yml
:Add adding some temporary commit to dirty the tree in the
contrib/reprobuild/Dockerfile.[release]
Related Issues
Checklist
Ensure the following tasks are completed before submitting the PR:
TODOs
have been addressed or removed.Additional Notes
master
, I've noticed @ShahanaFarooqui has made a few commits regarding the repro build process. Don't mean to be stepping on toes! I don't know if this work overlaps, and I'm hoping it still qualifies for the bounty, but if not, please consider it as an alternative submission to whatever planning around repro builds made since Aug. 2.