Repository navigation
[10.0] Backport shared CI bootstrap action - #9960
Merged
Merged
Conversation
Adapt 6acff31 (jruby#9866), retaining 10.0 setup-java/cache behavior, installed-JDK removal, and job ordering.
Member
Author
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.
Backport 6acff31 (#9866) to share bootstrap steps across 14 CI jobs and the distribution build, using master's action interface.
Preserve 10.0's setup-java@v5, Maven cache writes, installed-JDK removal, matrices, flags, permissions and secrets. Keep Ant after the distribution build and retain the installer's interleaved Java/install4j/build steps. The Maven plugin upgrade (46cf7df) and read-only precache setup (a42b640) are independent; 10.0 has no precache writer.
Validated action schema, actionlint, Bash syntax/ShellCheck, and expanded workflow equality against the base across 34 job/platform combinations. No new lint findings; existing duplicate-needs and shell diagnostics remain. No full JRuby build or GitHub-hosted jobs run locally.