You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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?
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.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
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.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think he meant that this local agent will not be dedicated because it shares some custom capabilities.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.