I'd like to setup a couple of my remote Bamboo agents to exclusively run a particular plan and not be available for any of my other plans. So for example if I have 10 remote agents set up with phpunit then any plan that requires phpunit sees all these 10 agents as potentially available to run on. But I want to set aside 2 of my remote agents to be sort of unavailable to run phpunit type plans unless the plan being executed is specifically "My Important Integration Plan".
I know you can set a required custom variable like "agent_name" should equal "bamboo.agent.8". But this only makes it so that "My Important Integration Plan" now only runs on bamboo.agent.8, but it doesn't prevent any of the other plans from still using bamboo.agent.8". Besides I want "My Important Integration Plan" to run on either bamboo.agent.8 or bamboo.agent.9.
Is there a way I can exclude certain agents from certain plans?
You'd have to:
There'll be a better way of doing this with Bamboo 5 (not sure if the UI for this will be exposed, but it will be doable).
This capability is really important to our company as we begin to roll out Bamboo to our enterprise. I was looking through the latest APIs and noticed I can add a BuildAgentRequirementFilter to Bamboo via plugin. The API has a strong warning that this is for internal use only and writing these incorrectly can severly impact Bamboo's operation.
Taking that warning in stride:
In some ad-hoc experimentation with this API on a dev instance, I noticed that I can return an empty collection of agents from this filter but the plan is still queued on the default agent -- doesn't run, but blocks the queue from other plans running. I can return a null collection which results in a stack trace in the log, but the plan is not queued. What is the proper way to implement such a filter or is there an alternative API to restrict which plans can run on a given agent?
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Bamboo 5.9 will no longer be supported after June 12, 2017. What does this mean? As part of our End of Life policy, Atlassian supports major versions for two years after the first major iteratio...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs