Adopt the Aspect Workflows GitLab component; simplify warming jobs#584
Merged
Conversation
GitLab CI now uses the aspect-build/aspect-workflows component (@2026.25.5) in every job via `extends: .aspect-workflows-setup`, matching how CircleCI (orb) and Buildkite (plugin) already use their integrations. The component waits for cache warming and writes /etc/bazel.bazelrc so raw `bazel` calls route through the runner's caches. Also drop the now-redundant `configure_workflows_env` and `agent_health_check` pre-steps from the warming jobs on all three providers (GitLab, CircleCI, and the GitHub warming workflow) — the setup integration handles environment config and waits for warming, so the explicit pre-steps are no longer needed.
Contributor
✨ Aspect Workflows Tasks📅 Fri Jun 19 00:06:11 UTC 2026 ✅ 12 successful tasks
⏱ Last updated Fri Jun 19 00:28:20 UTC 2026 · 📊 GitHub API quota 1,754/15,000 (12% used, resets in 58s, throttle 2×) |
The jobs used `before_script: [!reference [.aspect-workflows-setup, before_script]]`, but none of them has its own before_script to compose with — so the simpler, recommended `extends: .aspect-workflows-setup` form fits and matches the component README's primary pattern, the integration docs, and the release notes. `!reference` is only needed when a job already has a before_script.
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
1 participant
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.
Adopts the Aspect Workflows GitLab CI/CD component (
@2026.25.5) onmain, bringing GitLab to parity with CircleCI (orb) and Buildkite (plugin), which already use their integrations here..gitlab-ci.yml:includes the component and every job (build/test/format/lint/delivery + warming) usesextends: .aspect-workflows-setup. The component waits for the runner's cache warming and writes/etc/bazel.bazelrc, so rawbazelcalls route through the runner's remote cache, BES backend, and NVMe disk cache.warming.yaml): drop the now-redundantconfigure_workflows_envandagent_health_checkpre-steps — the setup integration handles environment config and waits for warming, so the explicit pre-steps are no longer needed.The component was verified end-to-end earlier (a prior test pipeline logged the setup step: runner metadata + "Wrote Workflows-tuned bazelrc to /etc/bazel.bazelrc", with
Group queue: aspect-defaultcorrect).Changes are visible to end-users: no
Test plan
circleci config validatepasses;.gitlab-ci.ymlparses; GitHubwarming.yamlhas no real actionlint errors.🤖 Generated with Claude Code