It would be realy nice to be able to have the possibility to configure a plan using some configuration file. That file could then be stored inside the repository of the project that needs building. The only thing left to do then is to tell Bamboo to create a plan from a certain repository. This would make a few things possible: * Having a (feature-)branch that needs different setup, without needing to configure an entire plan on Bamboo* And the reverse: you'd be able to run an old version or branch on the same plan. * Having a (formal) definition of what a build is for a certain project For example: the build-artefacts are now only stated in the bamboo plan, inspecting the repository won't tell you what artefacts are important. * No need to clone plans for similar-but-different builds * ... * Profit!! It would, of course, be possible to just create plans that run a standard script of some kind, but that would almost defy the use of Bamboo. Things like trend-lines, test result status, knowing what artefacts are important, are – imo – a key aspect of the Bamboo build ecosystem. Kind Regards, Matthias

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Configure plan from file

Matthias Hogerh

It would be realy nice to be able to have the possibility to configure a plan using some configuration file. That file could then be stored inside the repository of the project that needs building. The only thing left to do then is to tell Bamboo to create a plan from a certain repository.

This would make a few things possible:

Having a (feature-)branch that needs different setup, without needing to configure an entire plan on Bamboo
1. And the reverse: you'd be able to run an old version or branch on the same plan.
Having a (formal) definition of what a build is for a certain project
For example: the build-artefacts are now only stated in the bamboo plan, inspecting the repository won't tell you what artefacts are important.
No need to clone plans for similar-but-different builds
...
Profit!!

It would, of course, be possible to just create plans that run a standard script of some kind, but that would almost defy the use of Bamboo. Things like trend-lines, test result status, knowing what artefacts are important, are – imo – a key aspect of the Bamboo build ecosystem.

Kind Regards,

Matthias

Accepted answers

Tim Crall1

Feature requests should be posted at jira.atlassian.com - there are a number of similar requests there already (see https://jira.atlassian.com/browse/BAM-1223 and the issues it links to) - you can vote for these issues and watch them for progress. It seems like Atlassian has acknowledged and prioritized the request, but not announced any concrete release dates.

I agree that this would be an extremely valuable and indeed essential feature. I'm currently reading Jez Humble's book "Continuous Delivery" and it seems like this is a mandatory feature from his way of thinking.

All comments

pradhyumna shrestha

I would love to have this feature

Tim Crall1

Matthias Hogerh

Hi Tim,

Thanks for your explanation. I did some googling, but didn't come across BAM-1223 unfortunately. I'll upvote that ticket! smile I will make future feature-request at the correct place.

Adam Pryce

This is now available in Bamboo 6.0!

https://confluence.atlassian.com/bamboo/bamboo-6-0-release-notes-894743804.html

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bamboo