fix(ci): stop sigstore integration tests running on every PR#2609
Conversation
✅ Deploy Preview for ocm-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
The run_integration_tests matrix used a static `include` entry for bindings/go/sigstore/integration, which GitHub Actions injects unconditionally — even when the module is absent from the dynamic integration_test_modules_json list. This caused sigstore integration tests to run on every single PR regardless of what changed. Replace the matrix runner axis + exclude/include with a single module axis. Runner selection uses a top-level INTEGRATION_TEST_RUNNER_MAP env var (JSON object) looked up via fromJSON at job dispatch time, falling back to ubuntu-24.04-arm. The map is static and defined close to the job with instructions for adding further overrides. On-behalf-of: @SAP <jakob.moeller@sap.com> Signed-off-by: Jakob Möller <contact@jakob-moeller.com> On-behalf-of: @SAP <jakob.moeller@sap.com>
8928f29 to
e0a9ea5
Compare
Signed-off-by: Jakob Möller <contact@jakob-moeller.com> On-behalf-of: @SAP <jakob.moeller@sap.com>
0aa6b74 to
5562911
Compare
Signed-off-by: Jakob Möller <contact@jakob-moeller.com> On-behalf-of: @SAP <jakob.moeller@sap.com>
Summary
run_integration_testsmatrix had a staticincludeentry forbindings/go/sigstore/integration, which GitHub Actions injects unconditionally — even when the module is absent from the dynamicintegration_test_modules_jsonlist. This caused sigstore integration tests to run on every single PR.runneraxis +exclude/includewith a singlemoduleaxis. Runner selection uses a top-levelINTEGRATION_TEST_RUNNER_MAPenv var (JSON object) looked up viafromJSONat job dispatch time, falling back toubuntu-24.04-arm.Test plan
bindings/go/sigstore/(non-integration code) — sigstore integration tests should NOT appear in the matrixbindings/go/sigstore/integration/— sigstore integration tests SHOULD run onubuntu-latest.github/workflows/ci.yml— all tests run (CI changed path)ubuntu-24.04-arm