Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,736
Community Members
 
Community Events
176
Community Groups

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?

3 answers

1 accepted

1 vote
Answer accepted

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

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

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

0 votes

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.

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

Ken Wood Rising Star Aug 31, 2012

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.

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

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events