stevedlawrence opened a new pull request, #1432: URL: https://github.com/apache/daffodil/pull/1432
Although the release candidate container has helped to make builds reproducible and limit the amount of setup needed, it is still difficult to setup in some environments. This adds a custom GitHub action and workflow to build/publish release candidates, and a container to local build the same artifacts for reproducibility verification. To implement this, the new custom GitHub action is called "asf-release-candidate" and prepares the GitHub CI environment for creating a release candidate for ASF (it's mostly generic and could probably work with many other ASF projects with minor tweaks). This includes things like SBT settings for publishing to ASF maven repositories, creating directories for artifacts on dist.apache.org, importing signing keys, and creating the source artifact. Workflows using this action only need to publish artifacts (e.g. using sbt publishSigned) and write helper binaries to a provided artifacts directory. The post script of the action will then sign, checksum, and commit the artifacts. This also adds a new "Release Candidate" workflow that uses this custom action and is triggered when a release candidate tag is created, simplifing the release candidate process to just pushing a single signed tag. Workflow dispatch is allowed for testing, but it will not publish anything. A new container is also created called "build-release", which is essentially a simplified version of the current release candidate container, just without all the complexity related to publishing and closely matching the GitHub CI environment (e.g. switching to ubuntu), now handled by the custom action. When run, it creates all the same artifacts and puts them in a target/release/ directory--this can then be compared against published release artifacts to verify reproducibility. DAFFODIL-2971 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
