We have a Bamboo setup with about 30 build agents, and I have an incremental Gradle build. An incremental build benefits greatly from being run on the same agent every time. Is it possible to have make my build prefer its last build agent?
(1) Create a Requirement so that my build only runs on a specific single agent. But that only works so far: Other builds will start on that agent, and my build will have to wait for those to finish.
(2) Create a Requirement so that my build only runs on a small set of agents. I will still lose a lot of the benefits of the incremental builds.
(3) Reserve a agent for my build only. My operations dept doesn't want to do this, as the agent will stay idle a lot.
So that leaves my question: is there a way for my build to prefer its last build agent, but switch to a different one if the last agent is busy?
By the way, is it possible to create a "matches" requirement? All the agents have their own requirement keys: agent01.example.com, agent02.example.com, ... Is it possible to create a requirement that matches agent0.example.com? Or is it only possible to match on key content?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs