cleanup CI setup on 2.9.3 for pinterest

.buildkite/build.rayci.yml

@@ -51,6 +51,7 @@ steps:
       - oss
       - python
       - core_cpp
+      - disabled
     job_env: WINDOWS
     instance_type: windows
     commands:

.buildkite/core.rayci.yml

@@ -292,6 +292,7 @@ steps:
   - label: ":windows: python tests"
     tags:
       - python
+      - disabled
     job_env: WINDOWS
     instance_type: windows
     commands:
@@ -301,6 +302,7 @@ steps:
   - label: ":windows: core tests"
     tags:
       - core_cpp
+      - disabled
     job_env: WINDOWS
     instance_type: windows
     commands:

.buildkite/ml.rayci.yml

@@ -258,6 +258,7 @@ steps:
   - label: ":windows: train tests"
     tags:
       - train
+      - disabled
     job_env: WINDOWS
     instance_type: windows
     commands:

.buildkite/serve.rayci.yml

@@ -183,6 +183,7 @@ steps:
   - label: ":windows: serve tests"
     tags:
       - serve
+      - disabled
     job_env: WINDOWS
     instance_type: windows
     parallelism: 5

.rayciversion

@@ -0,0 +1 @@
+0.8.0

ci/build/build-manylinux-forge.sh

@@ -34,11 +34,12 @@ nvm use "$NODE_VERSION"
 
 # Install bazel
 npm install -g @bazel/bazelisk
-ln -s "$(which bazelisk)" /usr/local/bin/bazel
+ln -sf "$(which bazelisk)" /usr/local/bin/bazel
 
 {
   echo "build --config=ci"
   echo "build --announce_rc"
-  echo "build --incompatible_linkopts_to_linklibs"
-  echo "build:ci --remote_cache=${BUILDKITE_BAZEL_CACHE_URL}"
+  if [[ "${BUILDKITE_BAZEL_CACHE_URL:-}" != "" ]]; then
+    echo "build:ci --remote_cache=${BUILDKITE_BAZEL_CACHE_URL:-}"
+  fi
 } > ~/.bazelrc

ci/docker/manylinux.Dockerfile

@@ -1,7 +1,7 @@
 # syntax=docker/dockerfile:1.3-labs
 
 ARG HOSTTYPE
-FROM quay.io/pypa/manylinux2014_${HOSTTYPE}:2023-11-13-f6b0c51
+FROM quay.io/pypa/manylinux2014_${HOSTTYPE}:2024-07-02-9ac04ee
 
 ARG BUILDKITE_BAZEL_CACHE_URL
 
@@ -10,4 +10,5 @@ ENV RAY_INSTALL_JAVA=1
 ENV BUILDKITE_BAZEL_CACHE_URL=$BUILDKITE_BAZEL_CACHE_URL
 
 COPY ci/build/build-manylinux-forge.sh /tmp/build-manylinux-forge.sh
-RUN /tmp/build-manylinux-forge.sh
+
+RUN ./tmp/build-manylinux-forge.sh

ci/docker/manylinux.wanda.yaml

@@ -1,6 +1,6 @@
 name: "manylinux"
 froms:
-  - quay.io/pypa/manylinux2014_x86_64:2023-11-13-f6b0c51
+  - quay.io/pypa/manylinux2014_x86_64:2024-07-02-9ac04ee
 srcs:
   - ci/build/build-manylinux-forge.sh
 build_args:

python/README-building-wheels.md

@@ -9,10 +9,31 @@ produce .whl files owned by root.
 Inside the root directory (i.e., one level above this python directory), run
 
 ```
-docker run -e TRAVIS_COMMIT=<commit_number_to_use> --rm -w /ray -v `pwd`:/ray -ti quay.io/pypa/manylinux2014_x86_64  /ray/python/build-wheel-manylinux2014.sh
+docker run -ti --rm \
+    -e BUILDKITE_COMMIT="$(git rev-parse HEAD)" \
+    -e BUILD_ONE_PYTHON_ONLY=py39 \
+    -w /ray -v "$(pwd)":/ray \
+    quay.io/pypa/manylinux2014_x86_64:2024-07-02-9ac04ee \
+    /ray/python/build-wheel-manylinux2014.sh
 ```
 
-The wheel files will be placed in the .whl directory.
+The Python 3.9 wheel files will be placed in the `.whl` directory.
+
+One can change the value of `BUILDKITE_COMMIT` to generate wheels with
+different built-in commit string (the code is not changed) and
+`BUILD_ONE_PYTHON_ONLY` to build wheels of different Python versions.
+
+For arm64 / aarch64 architecture, use the `quay.io/pypa/manylinux2014_aarch64`
+image:
+
+```
+docker run -ti --rm \
+    -e BUILDKITE_COMMIT="$(git rev-parse HEAD)" \
+    -e BUILD_ONE_PYTHON_ONLY=py39 \
+    -w /ray -v "$(pwd)":/ray \
+    quay.io/pypa/manylinux2014_aarch64:2024-07-02-9ac04ee \
+    /ray/python/build-wheel-manylinux2014.sh
+```
 
 ## Building MacOS wheels