Fail CI when Gradle matrix generation fails - #11984
Conversation
Enable pipefail for the filtered matrix-generation pipelines so a failing Gradle invocation cannot be masked by jq. Valid empty matrices remain supported.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthroughThe CI workflow enables ChangesCI failure propagation
Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to This localized workflow change makes Gradle matrix-generation failures fail CI as intended, with no actionable merge-blocking risk remaining after normal checks and review. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Full details: Description checkExplanation The description explains the affected pipelines, the failure behavior, the Full details: Docstring CoverageExplanation No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.) ✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
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 dynamic Gradle matrix steps pipe Gradle output through jq. GitHub Actions runs these scripts with bash -e but without pipefail, so jq can return success after Gradle fails and leave the downstream matrix jobs skipped.
Enable pipefail for both filtered matrix-generation pipelines so Gradle failures fail the producer job. Successful empty matrices remain valid and continue to produce no matrix entries.
Summary by CodeRabbit