What’s new and updated in Buildkite
Agent names no longer support "%n"
Posted June 17, 2022 by Samuel
%n in agent names is deprecated and will soon be removed 👋
The default name for a Buildkite Agent used to be
agent-%n, resulting in
agent-2, etc. Pretty quickly, though, this gets tricky to keep unique, especially with a big database full of agent names. So to keep our database humming, we're removing support for
We began this process with Buildkite Agent v3.27.0 released on 8th February, 2021, removing
%n from the default agent name. Elastic CI Stack for AWS v5.2.0 was also updated to replace usage of
%spawn on the same day.
If you're running your agents another way, please review your agent configuration and confirm you're not using
If you are using
%n, there are a few alternatives:
- If you're running a single agent on each host, use
- If you're running multiple agents, use the spawn option and
- If neither of the previous options work, use
%randomwhich will turn into a few random characters.
Check out our docs for a complete reference:
We'll begin brownouts of
%n on Monday, 8th August 2022. Finally, we'll remove support for
%n on Monday, 5th September 2022. Agents which still use
%n in their name after this date will fail to connect and accept work.
If you need some more time, or have a problem completing this migration, please drop us an email to email@example.com.