- All playbooks
- Build every target framework in one parallel call
Build every target framework in one parallel call
Hand all target frameworks to the build tool at once so they build in parallel.
Company examples
How OpenAI used this technique
Read what OpenAI changed and follow the original sources.
Build every target framework in one parallel call
The .NET SDK's API export ran one MSBuild call per target framework in sequence. It now passes every framework to a single MSBuild invocation with BuildInParallel, and the export script adds -m.
API export builds every target framework in one parallel MSBuild call Source
- Use it when
- A build step builds several target frameworks or configurations one after another.
- Before applying it
- Parallel builds use more memory and CPU at once; confirm every target's output is identical.
Company Playbooks
- Read Anthropic’s playbookRun only affected tests
- Read DoorDash’s playbookRun build and test in parallel, sharded across CI agents
- Read Linear’s playbookBenchmark the same job on faster hardware
- Read Mastra’s playbookStarSling runners for the slowest test workflow
- Read OpenAI’s playbookRank CI fixes by the minutes they save
- Read Ramp’s playbookMove a CPU-bound test suite to a faster CPU
- Read Shopify’s playbookLet an agent iterate against one CI metric
- Read Spotify’s playbookBuild arm64 on native arm64 runners
- Read Stripe’s playbookRun only the tests a change can reach
- Read Uber’s playbookBuild the merge-queue speculations most likely to be needed