Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

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

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

 

 

1 answer

1 accepted

0 votes
Answer accepted

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.

Suggest an answer

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

Bamboo 101 Video

G’day Community! As we gear up to introduce Bamboo Data Center to the world, we wanted to make sure that we shared a bit more about Bamboo, the product. Our team has put together an overview video ...

190 views 4 6
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