Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-13600

Build and deployment templates



    • Suggestion
    • Resolution: Done
    • 6.0.0
    • Plugins, REST API
    • None
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.


      My company currently has 150+ code repositories (common libraries, plugins, front-ends, tools, etc), each of which is represented by a Plan in Bamboo, and each of these Plans execute the exact same build pipeline sequence of Stages/Jobs/Tasks via the use of paramaterised tasks. The only field that differs from Plan to Plan is the Source repository that Plan is associated with.

      The issue is that if for example I wanted to add a common "Generate Reports" job for each plan, I have to manually add this Job and it's tasks to all 150+ plans - which is quite time consuming and monotonous, not to mention prone to introducing inconsistencies between plans over time.

      A way to greatly reduce the amount of time required to update a large number of plans with the exact same Stages/Jobs/Tasks pipeline would be a huge help.

      Two potential solutions are:

      1) Implement some form of "Plan template" that a plan could inherit from. Then any subsequent changes to the template would propagate through all plans associated with it.

      TeamCity CI Server has an implementation along these lines: http://confluence.jetbrains.com/display/TCD8/Build+Configuration+Template

      2) Enhance the current "Plans -> Bulk Action" functionality to allow for the adding/removing of Stages/Jobs to multiple plans at a time.


        Issue Links



              Unassigned Unassigned
              302c74ac-7af9-46bf-b6c1-7db753d54b11 Deleted Account (Inactive)
              244 Vote for this issue
              180 Start watching this issue