ci: run the new-grammar-engine unit tests in parallel (Jenkins) (#467)#488
Open
SJrX wants to merge 1 commit into
Open
ci: run the new-grammar-engine unit tests in parallel (Jenkins) (#467)#488SJrX wants to merge 1 commit into
SJrX wants to merge 1 commit into
Conversation
The Jenkins "Build" stage only ran tests on the original engine (via `build`). Wrap it in a parallel block (mirroring the Assemble Metadata stage): one branch builds, tests (original engine) and publishes; a second branch runs the unit tests against the new list-of-successes engine (-Dsystemd.unit.grammarParseEngine=true) in its own Kubernetes pod, so the two engine runs are genuinely parallel with no shared workspace. Refs #467 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
What
Makes the Jenkins pipeline run the unit suite against both validation engines, in parallel. The "Build" stage previously only tested the original engine (via the
buildtask); now it's aparallelblock (mirroring the existingAssemble Metadatastage):./gradlew … test -Dsystemd.unit.grammarParseEngine=true.Separate pods ⇒ separate workspaces ⇒ no
build/clobbering, and the two runs are genuinely concurrent (not sequential).Notes
unstashof the generated metadata so it can compile, and drops-PbuildScan(no scan/auth needed for the parity run).parallel { stage{agent…} stage{agent…} }pattern in this file. The publish branch's inner indentation is left unchanged to avoid risky reformatting.Refs #467
🤖 Generated with Claude Code