---
title: "Package other architectures on the runner that is free"
description: "Run packaging that executes no target code on the runners that are available."
url: https://starsling.dev/ci-playbooks/techniques/package-on-available-runner
canonicalUrl: https://starsling.dev/ci-playbooks/techniques/package-on-available-runner
---

# Package other architectures on the runner that is free

Run packaging that executes no target code on the runners that are available.

## How to choose an approach

This technique currently has one documented company example. Validate its prerequisites, tradeoffs and original CI environment against your repository before adapting it.

- **[OpenAI](https://starsling.dev/ci-playbooks/openai#package-on-available-runner)**: Use it when A packaging job for another architecture waits on a scarce runner while executing no target code. Check before adopting: Any step that executes the target's binaries still needs its native runner.

## Apply this technique

````text
Evaluate and apply this CI technique to my repository: Package other architectures on the runner that is free.

Run packaging that executes no target code on the runners that are available.

Read the technique and its source-backed company examples: https://starsling.dev/ci-playbooks/techniques/package-on-available-runner.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.
````

## How OpenAI used this technique

Read what OpenAI changed and follow the original sources.

### OpenAI: Package other architectures on the runner that is free

Codex's ARM64 Windows packaging job only downloads, signs, archives and compresses. It now runs on x64 runners alongside the x64 packaging job.

Evidence: Source PR/commit evidence

In one release run the ARM64 packaging job waited 76s for its runner and held the release 1m43s after x64 finished ([Source](https://github.com/openai/codex/pull/28001))

Use it when: A packaging job for another architecture waits on a scarce runner while executing no target code.

Before applying it: Any step that executes the target's binaries still needs its native runner.

[Read more in the OpenAI playbook](https://starsling.dev/ci-playbooks/openai#package-on-available-runner)

[Primary source](https://github.com/openai/codex/pull/28001)

## CI optimization is continuous work.

Apply this technique yourself, or use StarSling Runners for faster GitHub Actions and optional agent-driven optimization PRs, which teams on eligible paid plans can turn on.

[Get self-improving CI](https://starsling.dev/products/runners)

## Company Playbooks

### [Anthropic](https://starsling.dev/ci-playbooks/anthropic)

Run only affected tests

### [DoorDash](https://starsling.dev/ci-playbooks/doordash)

Run build and test in parallel, sharded across CI agents

### [Linear](https://starsling.dev/ci-playbooks/linear)

Benchmark the same job on faster hardware

### [Mastra](https://starsling.dev/ci-playbooks/mastra)

StarSling runners for the slowest test workflow

### [OpenAI](https://starsling.dev/ci-playbooks/openai)

Rank CI fixes by the minutes they save

### [Ramp](https://starsling.dev/ci-playbooks/ramp)

Move a CPU-bound test suite to a faster CPU

### [Shopify](https://starsling.dev/ci-playbooks/shopify)

Let an agent iterate against one CI metric

### [Spotify](https://starsling.dev/ci-playbooks/spotify)

Build arm64 on native arm64 runners

### [Stripe](https://starsling.dev/ci-playbooks/stripe)

Run only the tests a change can reach

### [Uber](https://starsling.dev/ci-playbooks/uber)

Build the merge-queue speculations most likely to be needed