Give build queries the same startup flags as the build

Run target-discovery queries on the same build-tool server as the build that follows.

Prompt

Evaluate and apply this CI technique to my repository: Give build queries the same startup flags as the build.

Run target-discovery queries on the same build-tool server as the build that follows.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/share-bazel-startup.md

Inspect this repository’s CI workflows, build and test commands, dependencies, and recent run timings. Identify where this technique applies and explain the expected benefit using this repository’s evidence.
Measure a baseline from recent comparable runs: elapsed time, queue time, runner minutes and failures where available. If data is unavailable, say what cannot be measured.
Compare relevant company approaches, checking prerequisites, platform differences and tradeoffs. Rank applicable options by evidence, fit and measurable opportunity; do not present company results as predictions for this repo.
Recommend the smallest safe change, show what checks and fallback paths remain, and ASK ME WHICH CHANGE TO APPROVE BEFORE EDITING ANY FILES.
Only after approval, work on a new feature branch, make one reversible change, and open a reviewable pull request. Never merge or push to a default or protected branch.
Keep required checks, test coverage, deployment and release behavior intact. Validate the change and compare equivalent runs where possible; report limitations and what should be monitored after merge.

View all playbooks

How OpenAI used this technique

Read what OpenAI changed and follow the original sources.

How OpenAI used this technique

Give build queries the same startup flags as the build

Company Playbooks