ci: parallelize Go module tests and Scripts-and-Compose into matrix jobs - #1604
Merged
Conversation
Both jobs ran a long sequence of fully independent checks in a single runner, serially. Split each into a matrix (fail-fast: false, one runner per entry) plus a thin aggregator job that preserves the original check name for anything watching it: - go: was a shell loop over every go.mod running `go test ./...` one module at a time (22 modules). Now go-fmt (whole-repo gofmt check, unchanged) + go-test (one matrix entry per module) + go-modules- complete (aggregates both under the original "Go formatting and tests" name). - scripts-and-compose: 34 independent named steps (Python/shell/Go script tests, real-Keycloak integration tests, YARA/compose validation) run one after another in one job. Now one matrix entry per check, all sharing one setup preamble (checkout + python + go), plus scripts-and-compose-complete aggregating under "Scripts and Compose". Every check's own explanatory comment moved with it unchanged -- verified programmatically against the original file (line-for-line content match) before splicing, not hand-retyped. No check's actual command changed, only how many runners execute them concurrently. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
This was referenced Aug 17, 2026
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.
Both the
goandscripts-and-composeQuality workflow jobs ran a long sequence of fully independent checks serially on one runner. This splits each into a matrix job (one runner per entry,fail-fast: false) plus a thin aggregator job that keeps the original check name for anything watching it (branch protection, status checks):go-fmt(unchanged whole-repo gofmt check) +go-test(one matrix entry per Go module, 22 total) +go-modules-complete(aggregates both under the original "Go formatting and tests" name).scripts-and-compose-completeaggregating under the original "Scripts and Compose" name.No check's actual command changed — only how many runners execute them concurrently. Every check's own explanatory comment moved with it unchanged; verified programmatically (line-for-line content match against the original file) before splicing rather than hand-retyped, given the size.
This PR's own CI run is the first real test of the new structure.