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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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.

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.

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.

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

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bamboo

Bamboo 7.2 is here!

I'm happy to announce that Bamboo 7.2 has been released and it’s overflowing with awesome new features. This will be the last major Server release before the launch of Bamboo DC. Bamboo logs We...

513 views 5 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you