Is there a way to avoid shared remote capabilities being inherited in new bamboo agents?

[prasantk]

Hi,

We've an existing on premise bamboo infrastructure with several remote agents. To manage the increasing workload, we had setup some additional remote agents running on cloud. We only want 'docker' as a capability for the new agents and would want to avoid the existing shared remote capabilities on these new agents. The existing shared remote capabilities should be used as-is by the current on premise remote agents. The problem is that these new agents running on cloud seems to inherit the existing shared remote capabilities when connected to the on premise bamboo master. 

Could you please suggest how we can avoid existing shared remote capabilities being inherited in the new bamboo agents?

Any help or pointers is much appreciated!

Thanks and Regards,

Prasant Kumar

[Daniel Santos · Accepted solution]

Hi @prasantk

The behavior you are experiencing is indeed expected. Shared capabilities will be inherited by every remote agent available.

There is an improvement request to split it into sections specifically to solve a problem that shows up when using multiple OS platforms ([BAM-20114] Shared remote capabilities should have agent type distinction (OSX, Linux, Windows, ...)). Maybe adding an extra comment in that feature request describing your scenario would be helpful when our devs start designing this feature.

Could you please suggest how we can avoid existing shared remote capabilities being inherited in the new bamboo agents?

You will need to remove the shared capabilities that you don't want to in all your remote agents and created them directly on the agents. To create the capabilities you can use the method described in this article: Configuring remote agent capabilities using bamboo-capabilities.properties.