Hi everyone! In Bamboo 6.0 we have introduced 'Bamboo Specs', which lets you define entire plan (and deployment since Bamboo 6.1) configuration as code. This is a great way to have templating for plans and a single place to configure various properties. Try it out! See documentation:

• https://confluence.atlassian.com/bamboo/bamboo-specs-894743906.html
• https://confluence.atlassian.com/bamboo/bamboo-6-0-release-notes-894743804.html
• https://confluence.atlassian.com/bamboo/bamboo-6-1-release-notes-932387968.html
• https://confluence.atlassian.com/bamboo/bamboo-6-2-release-notes-938641951.html 

I also vote for hierarchy or Jenkins-style templates where changing the "template" or "parent" causes everything linked to it to change. This would include jobs in the plan.

Hi jerryjvl,

Templates are not on our near term roadmap at this time.

Please watch and vote for BAM-11380 if you are interested in Atlassian implementing templates for Bamboo.

Thanks,
James Dumay
Product Manager

Plan Branches look like a very useful feature, but just to be clear, this obviously does not address the actual issue discussed here.

I am evaluating a broader set of Atlassian tools for my company where we currently only use Confluence at this time. Bamboo looks like an excellent tool, but we will need templates to keep the workload manageable for much the same reasons that everybody else mentions.

We have 100+ applications in separate Git repositories to maintain that all broadly share a common build plan, except for slight variations in the detail. If we have to maintain 100+ separate build plans that will make Bamboo virtually useless to us.

Every once in a while due to changes/improvements to our SDLC processes we have to tweak our common build plan, but without a Template feature this would mean we have to go in and manually update 100+ plans and hope we do not make a mistake somewhere.

Is there any more clarity when a full plan templating feature might become part of Bamboo?

Hi all,

This week we have introduced a new feature called plan branches as part of Bamboo 4.0.

While this feature is targeted mostly around having a build for each branch without having to duplicate build configuration, it can also be used as a lightweight build templating system. When you define a plan branch, it inherits all of the build configuration defined in the parent (default) plan with the option of overriding plan variable values.

Take a look and let us know what you think.

Thanks
James

Glad to see progress on bulk edit but IMHO this is at least as important.

IMHO, a bulk edit wouldn't be good enough. In a bulk edit scenario, I would have to know about all the plans that should be edited. The friction point is not only having to edit plans one by one. The other friction point is having to maintain the plans who's build processes are similar.

One of the nice features of TeamCity is build plan inheritance. I can define a base plan with build plan settings, environment variables, artifacts, etc. Child plans that inherit from this build plan can choose to override any of these settings or add more settings. When I want to add an artifact or change a setting, all I would have to do is add it to the base plan & all the plans that inherit from that plan will inherit this new artifact or setting.

we are looking towards a bulk edit feature in Bamboo which allows you to concurrently modify many plans together.