Community
Products
Bamboo
Questions
Restrict a plan to a specific local agent

Restrict a plan to a specific local agent

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?

2 answers

1 accepted

1 vote

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

0 vote

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.

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

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.