Repository navigation
[ci] Explain the glibc 2.17 Bazel build and mark it for removal - #68113
Draft
elliot-barn wants to merge 1 commit into
Draft
elliot-barn wants to merge 1 commit into
elliot-barn wants to merge 1 commit into
Conversation
elliot-barn
force-pushed
the
elliot-barn/bazel-protobuf-29
branch
from
November 12, 2026 22:44
c867d2a to
59c6539
Compare
elliot-barn
force-pushed
the
elliot-barn/bazel-glibc217-todos
branch
from
November 12, 2026 22:45
a0f007e to
d75d296
Compare
Comment the bazel-glibc217 steps with why they exist: Bazel 8's release binaries need glibc >= 2.25 and the wheels build in manylinux2014 (glibc 2.17). Add TODOs on the steps, their depends_on edges and the Dockerfile COPY blocks to remove all of it once the wheel build moves to manylinux_2_28. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Signed-off-by: elliot-barn <elliot.barnwell@anyscale.com>
elliot-barn
force-pushed
the
elliot-barn/bazel-glibc217-todos
branch
from
November 12, 2026 23:03
d75d296 to
d720fcd
Compare
This branch has not been deployed
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.
Why
Stacked on #66483, and based on its branch, so the diff is only the comments. GitHub retargets it to master once #66483 merges.
#66483 adds a
bazel-glibc217wanda image: Bazel compiled from source inside manylinux2014, shipped with a JDK 21. Bazel 8's official Linux binaries need glibc >= 2.25. Ray builds its Linux wheels inside manylinux2014 (CentOS 7, glibc 2.17), so that the wheels keep running on glibc 2.17 systems, and the official binary can't start there.The steps that build and use this image don't say why they exist, or when they can go. This PR adds that.
What changes
Comments only, no behavior change:
bazel-glibc217-x86_64step (.buildkite/_forge.rayci.yml): why the image exists, and a TODO to move the wheel build from manylinux2014 to manylinux_2_28 (glibc 2.28, which raises the user glibc floor to 2.28). After that move, the official Bazel binary runs in the build image and all of this can be deleted. The comment lists everything to remove.bazel-glibc217-aarch64step (.buildkite/linux_aarch64.rayci.yml): a short version that points to the x86_64 step.depends_on: bazel-glibc217-*edge (_forge,_wheel-build,build,linux_aarch64): a one-line TODO.COPY --from=bazelblocks in the ray-core, ray-cpp-core, ray-java and manylinux-retag Dockerfiles: a one-line TODO.The release pipeline's
_forgeand_wheel-buildfiles are symlinks to these, so they pick up the same comments.Tests run
yaml.safe_loadon every.buildkite/*.rayci.ymlpre-commit run --files <changed files>AI assistance was used to draft this change.
🤖 Generated with Claude Code