Run Results regression on toolchain PR path changes - #64
Merged
Merged
Conversation
Schedule-only triggering hid the missing JDK 21 until Wednesday. Also run the strict Results workflow when this file or the Results/lang installers change so the next toolchain gap fails on the PR. Co-authored-by: jmjava <jmjava@gmail.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
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.
Summary
dom, and Go on the scheduled Results workflowWhy this is the live check
This path filter starts
results-regressionon this PR, so the first JDK 21 Results run does not have to wait for next week's cron.Companion
The M17 aggregate already includes this trigger in #63.
Verification
libs/tekton-dag-common/tests/test_m17_results_automation.py: 2 passedbash scripts/run-regression-agent.sh:regression exit code: 0(local-only; no kubectl). Maven compiledbaggage-spring-boot-starterwith JDK 21, PHPUnit 19/19, operator Go tests passed