feat: add release build workflow with comparison against release script#75
Closed
skjnldsv wants to merge 1 commit into
Closed
feat: add release build workflow with comparison against release script#75skjnldsv wants to merge 1 commit into
skjnldsv wants to merge 1 commit into
Conversation
Builds Nextcloud release archives independently and compares them against the release script's assets on the same GitHub release. Triggers on release:published (parallel with changelog workflow) and workflow_dispatch for testing against existing releases. Build pipeline: - 29 parallel fetch+build jobs (composer, .nextcloudignore, dev cleanup) - Docs from documentation gh-pages - Assemble: merge, version.php, sign, metadata, tar.bz2+zip+checksums - Compare: downloads release script assets from the same release, diffs file lists, reports in step summary Build configs in build/ directory (stable32-34 + master). Signed-off-by: John Molakvoæ (skjnldsv) <skjnldsv@protonmail.com>
Contributor
Author
|
Merging into #74 as part of the orchestrator refactor. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a GitHub Actions workflow that builds Nextcloud release archives independently and compares the output against the release script's assets, on the same release.
This runs in parallel with the existing changelog workflow. Once the output matches the release script consistently, the release script can be retired and this workflow takes over publishing.
How it works
release: published(same event as changelog) orworkflow_dispatchnextcloud/structure, update version.php, sign, create archivestar.bz2from the same GitHub release, diff file listsThe compare step downloads the assets that the release script attached to the same release. Since both build from the same branch HEAD at the same time, the diff should be near-zero. Any differences indicate bugs in either the workflow or the release script.
Build configs
Per-version configs in
build/directory:build/stable32.json/build/stable33.json: 27 componentsbuild/stable34.json/build/master.json: 29 components (+files_lock, +office)Secrets needed
SIGN_PRIVATE_KEYSIGN_CERTIFICATERELEASE_TOKENTest plan
workflow_dispatchwith tagv33.0.4to test against existing releaserelease: publishedtrigger