Restrict a plan to a specific local agent

[Sean Dockery]

We have six build plans that we run manually about once a month to perform a comprehensive set of regression tests of integration between various products that we develop. The longest running of these plans is approximately 50 hours in length.

Is there a way in which I can configure the plans to have an affinity to a specifc local agent so that we can prevent them from saturating our build queues?

[Adam Myatt · Accepted solution]

Sean - The Bamboo Group Agent plugin should be able to help you. https://marketplace.atlassian.com/plugins/com.edwardawebb.bamboo-group-agent

[Sean Dockery]

Thanks, Adam. At first glance, this looks to be exactly what I need.

[Przemek Bruski]

The simplest approach would be to add a custom capability (e.g. longRunningJobAgent) to that agent and add a requirement for that capability on these 6 jobs.

[Sean Dockery]

The problem is that you cannot add custom capabilities to individual local agents.

[Ken Wood]

You can't? That's news to me. I have two builds that need to share a resource (exclusive) so I defined "gateResourceX" as a capability on one and only one local agent. Then, both build plans have a requirement for "gateResourceX" exists. Which ever build plan gets to that specific local agent first, the other build plan is forced to wait in the queue until the agent is no longer being used.

[Bastien Chong]

I think he meant that this local agent will not be dedicated because it shares some custom capabilities.

[Kidane Yosief]

I think Dedicated agent was enough solution to my problem. I had the problem of running two jobs and fails if they run at the same time. Now I am able to block them using the dedicated agent feature. Thanks