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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,719
Community Members
 
Community Events
176
Community Groups

ISO method for Elastic Bamboo activation on a per-Build-Plan basis

We're finally starting to use Elastic Bamboo after having used a single monolithic Bamboo host for a long time.

Most of our Bamboo jobs are amenable to being run under Elastic Bamboo but some are not.   Furthermore we'd like to primarily control the use of Elastic Bamboo on a per-Plan basis, with a few hand-curated exceptions for specific jobs.

This would be easy if one could use Bamboo variables as values of Requirements, but apparently you cannot despite a ticket which has been out there for many years (BAM-12232).

E.g. is there a relatively easy way to use an API to remotely manage these Requirements?    At this time we'd like to continue to hand-edit our Plans, scripts, etc within the Bamboo UI, but it could make sense to manage only the Requirements via an API.

We're running Bamboo version 6.5.0 build 60509.

Thanks in advance for your suggestions.

1 answer

1 vote

Jonathan,

You specified two requirements (remote management of Plan's requirements and hand-editing of Plan configuration) which Bamboo is not able to handle simultaneously.

In my opinion your best bet is to move your plan configuration to Bamboo Specs and manage your configuration entirely from the code.

Cheers,

Krystian Brazulewicz
Bamboo Team

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events