Solution skill
Buildkite: agents property inside matrix.adjustments breaks pipeline upload
Complete solution
Shows how to fix buildkite: agents property inside matrix.adjustments breaks pipeline upload. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Use separate steps per platform or a dynamic pipeline generator for per-combination queue routing.
Steps
- [buildkite/skills]: putting
agents:insidematrix.adjustmentsfails pipeline upload with 'agents is not a valid property on the matrix.adjustments configuration'. Use separate steps per platform or a dynamic pipeline generator for per-combination queue routing. Another classic: Docker Compose steps produce artifacts but the agent cannot find them, because files created inside containers are invisible to the host agent; mount the working directory as a volume so container outputs are visible forartifact_paths:. And keep dynamic pipelines under about 500 generated steps; beyond that the UI degrades.
When to use
You are seeing this: [buildkite/skills]: putting agents: inside matrix.adjustments fails pipeline upload with 'agents is not a valid property on the matrix.adjustments configuration'. Use this skill when you run into "Buildkite: agents property inside matrix.adjustments breaks pipeline upload".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Evidence
Source: Two pipeline-config mistakes that produce confusing errors, from Buildkite's own skill guidance.
Verified resolution: [buildkite/skills]: putting agents: inside matrix.adjustments fails pipeline upload with 'agents is not a valid property on the matrix.adjustments configuration'. Use separate steps per platform or a dynamic pipeline generator for per-combination queue routing. Another classic: Docker Compose steps produce artifacts but the agent cannot find them, because files created inside containers are invisible to the host agent; mount the working directory as a volume so container outputs are visible for artifact_paths:. And keep dynamic pipelines under about 500 generated steps; beyond that the UI degrades.
Source URL: https://github.com/buildkite/skills/blob/HEAD/steering/pipelines.md
By @issueatlas · Version 3 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_OIRrv-5a5KY-2agSHzRnLA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Buildkite: agents property inside matrix.adjustments breaks pipeline upload <span>— Vectle</span></a>