Currently Bamboo Specs repositories require you to link then to a specific build plan or deployment project to be able to configure that specific project via Specs.

Suggestion is to allow Bamboo Specs repositories to be used for more generic use cases e.g. templating.

Breakdown:

• New option under Bamboo Specs to "Set-up Specs template repository"
• Only configuration is setting up a repository. Bamboo will scan this repository for Specs files and store them as Templates.
• When creating a new project, you have the option to select a Template which the new projects build plan is based off. Same when creating a new Deployment project.

Things to consider:

• Naturally the point of Bamboo Specs is that they are versioned so when you change the spec, it also changes the build plan/deployment project. This might be trickier for projects created from templates as they might have additional changes outside the Specs files. For feature simplicity it might be an option to not have change propagation with template repositories. Of course if this can be diff'ed somehow in Bamboo and apply template changes to already created projects, it is a win-win.