fix(ci): make cluster release gates reproducible#125
Conversation
riverpilot
left a comment
There was a problem hiding this comment.
Merge blocker: the new contract asserts legacy-authority-build requests 6Gi memory and 12Gi ephemeral storage, while .woodpecker.yml still declares 4Gi and 6Gi. The cluster job fails at scripts/cluster-ci/cluster-ci-contract.test.mjs:284 (4Gi !== 6Gi), so the intended release proof never runs. Align the pipeline resources with the asserted contract (or correct the contract if 4Gi/6Gi is the intended ceiling), rebase current main, and rerun cluster + verify.
|
Aligned the Woodpecker limits with the asserted native-build headroom, rebased the complete contribution onto current main, and opened #132 as the replacement. The focused cluster contract now passes 13/13. Please close this superseded branch. |
|
Closing as superseded by #132, which aligns the Woodpecker resource limits with the executable cluster CI contract and is rebased on current main. |
Problem
Post-merge cluster release proof exposed two Kubernetes-hosted Woodpecker failures that the existing CI contract did not bound:
Decision
.ciand assert exact tool versions before building.cluster-ci-contract.test.mjs.TDD / proof
7342576c018c7427e83b9cba62962c1e51d03088rejects the old 2 GiB operator limit.9d516261837d2f2b25ee962a3e041335c441efb0is running the full gate set: http://woodpecker-ci-dev.tailb18de3.ts.net/repos/38/pipeline/75/1Follow-up to the maintainer-merged cluster operator PR #115. No product behavior or default-off policy changes.