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

[Jonathan Epstein]

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.

[Krystian Brazulewicz]

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