[draft] ci: add pinned Linux CI image recipe and offline validation - #5511
Open
pingzh wants to merge 1 commit into
Open
[draft] ci: add pinned Linux CI image recipe and offline validation#5511pingzh wants to merge 1 commit into
pingzh wants to merge 1 commit into
Conversation
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.
Which issue does this PR close?
Part 1 of #5490. This PR does not close the issue; image publication and CI adoption will follow separately.
Rationale for this change
Linux Spark CI jobs repeatedly install toolchains and download the same dependencies. Before switching those jobs to a prebuilt image, we need a pinned toolchain recipe and a check that its dependency caches are sufficient without carrying forward Comet binaries or previous build outputs.
What changes are included in this PR?
/opt/comet-ci. The final image starts from the toolchain stage and excludes Comet artifacts, SNAPSHOTs, local Maven installations, credentials, and workspace build outputs.Publishing, scheduled refreshes, digest-based adoption, rollback, and performance measurements are outside this PR.
How are these changes tested?
python3 dev/ci/images/test_image.py: 21 tests passed.-DskipTests, with test classes compiled), Catalyst/SQL/Hive test compilation, and 104 Spark smoke tests: 42 inLiteralExpressionSuiteand 62 inMathFunctionsSuite.COMET_CI_BUILD_JOBS=16 bash dev/ci/images/validate.sh: passed the same builds and all 104 smoke tests in a fresh container with--network=none, an empty runtime home, and no host dependency-cache mounts.