mirror of
https://github.com/openai/codex.git
synced 2026-09-06 15:29:32 +00:00
7226904ed1
## Why CI jobs repeat common bootstrap steps, which makes it harder to keep Bazel and Cargo lanes aligned. Centralizing the lightweight setup gives us one place for future runner-wide optimizations without adding Rust toolchain or component installation to the Windows Bazel long poles. ## What - add zero-input `.github/actions/setup-ci` to set Cargo's git transport, install DotSlash and `just`, expose DotSlash from stable PATH locations, and enable Windows Git long paths - have `setup-bazel-ci` compose the common setup, then remove its DotSlash/test-prerequisite plumbing - migrate Bazel, Cargo CI, V8 canary, repo checks, nextest, and Windows release call sites while keeping Rust toolchain and MSVC setup explicit - preserve the existing nextest Dev Drive setup unchanged ## Validation - `just test-github-scripts` (30 tests) - parsed workflow and composite-action YAML with `yq`
60 lines
2.5 KiB
YAML
60 lines
2.5 KiB
YAML
name: prepare-bazel-ci
|
|
description: Prepare a Bazel CI job with shared setup, repository cache restore, and execution logs.
|
|
inputs:
|
|
target:
|
|
description: Target triple used for setup and cache namespacing.
|
|
required: true
|
|
cache-scope:
|
|
description: Logical namespace used to keep concurrent Bazel jobs from reserving the same repository cache key.
|
|
required: true
|
|
outputs:
|
|
repository-cache-path:
|
|
description: Filesystem path used for the Bazel repository cache.
|
|
value: ${{ steps.setup_bazel.outputs.repository-cache-path }}
|
|
repository-cache-key:
|
|
description: Primary actions/cache key for the Bazel repository cache.
|
|
value: ${{ steps.cache_bazel_repository_key.outputs.repository-cache-key }}
|
|
repository-cache-hit:
|
|
description: Whether the Bazel repository cache restore found an exact key match.
|
|
value: ${{ steps.cache_bazel_repository_restore.outputs.cache-hit }}
|
|
|
|
runs:
|
|
using: composite
|
|
steps:
|
|
- name: Set up Bazel CI
|
|
id: setup_bazel
|
|
uses: ./.github/actions/setup-bazel-ci
|
|
with:
|
|
target: ${{ inputs.target }}
|
|
|
|
- name: Compute bazel repository cache key
|
|
id: cache_bazel_repository_key
|
|
shell: bash
|
|
env:
|
|
CACHE_SCOPE: ${{ inputs.cache-scope }}
|
|
TARGET: ${{ inputs.target }}
|
|
CACHE_HASH: ${{ hashFiles('MODULE.bazel', 'codex-rs/Cargo.lock', 'codex-rs/Cargo.toml') }}
|
|
run: |
|
|
echo "repository-cache-key=bazel-cache-${CACHE_SCOPE}-${TARGET}-${CACHE_HASH}" >> "${GITHUB_OUTPUT}"
|
|
echo "repository-cache-restore-key=bazel-cache-${CACHE_SCOPE}-${TARGET}-" >> "${GITHUB_OUTPUT}"
|
|
|
|
# Restore the Bazel repository cache explicitly so external dependencies
|
|
# do not need to be re-downloaded on every CI run. Keep restore failures
|
|
# non-fatal so transient cache-service errors degrade to a cold build
|
|
# instead of failing the job.
|
|
- name: Restore bazel repository cache
|
|
id: cache_bazel_repository_restore
|
|
continue-on-error: true
|
|
uses: actions/cache/restore@668228422ae6a00e4ad889ee87cd7109ec5666a7 # v5.0.4
|
|
with:
|
|
path: ${{ steps.setup_bazel.outputs.repository-cache-path }}
|
|
key: ${{ steps.cache_bazel_repository_key.outputs.repository-cache-key }}
|
|
restore-keys: |
|
|
${{ steps.cache_bazel_repository_key.outputs.repository-cache-restore-key }}
|
|
|
|
- name: Set up Bazel execution logs
|
|
shell: bash
|
|
run: |
|
|
mkdir -p "${RUNNER_TEMP}/bazel-execution-logs"
|
|
echo "CODEX_BAZEL_EXECUTION_LOG_COMPACT_DIR=${RUNNER_TEMP}/bazel-execution-logs" >> "${GITHUB_ENV}"
|