Harden and simplify CI/CD pipeline - #2
Draft
skilledwolf wants to merge 4 commits into
Draft
Conversation
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
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.
What
Rebuild the fork's CI/CD around a small required gate, a strict scheduled compatibility sweep, and an sdist-first release pipeline.
-fpermissivecoverage realpypienvironment and OIDCGatecheck for branch protectionWhy
The previous matrix looked broad but two important axes were ineffective: it passed
Boost_ROOT_DIRwhile ALPS consumesBoost_SRC_DIR, and CMake always appended-fpermissive. Its per-run cache keys created 117 caches / 12.26 GB in under four hours, while an uncapped 39-job sweep amplified hosted-runner mirror stalls. Releases could publish from anyv*tag, and PR validation did not exercise the actual sdist-to-wheel path.Impact
PRs now spend capacity on four meaningful support-boundary builds plus one package smoke test. The weekly run is reduced to fourteen strict compatibility/canary builds. Remote compiler caches are limited to four labels, saved only on
master, and rotate weekly. Manual release runs are build-only; only a published GitHub Release whose tag exactly matchesproject.versioncan request PyPI OIDC credentials.Local verification
actionlint -shellcheck shellcheck .github/workflows/*.ymlshellcheck .github/scripts/*.shjq empty .github/ci-matrix/*.jsonpython3 -m py_compile .github/scripts/*.pyzizmor --pedantic --no-config .github/workflows(zero findings)pyalps-2.3.4b1.tar.gz, passedtwine check, and enumerated cibuildwheel targets from that sdistgit diff --check