• Icon: Suggestion 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.

            [BAM-13600] Build and deployment templates

            Hello, we are also looking forward to have some information about this. We are evaluating the Atlassian Suite and this is a "MUST HAVE" 

            Federico Fortini added a comment - Hello, we are also looking forward to have some information about this. We are evaluating the Atlassian Suite and this is a "MUST HAVE" 

            tien tran added a comment -

            I'm using bamboo version 6.3.1 build 60306, but still dont know what exact solution for it. What do we have to support this case if we marked this ticket resolved without any solution.

            What mentioned in this ticket's description is not truly a solution.

            The 1st way just only re-use stage idea, not a completely build plan template.

            The 2nd one is not entirely template, it required we clone a lot of build plan (manually) then replace them whenever we need.

            Still wait for update from bamboo team on this concern.

            Thank you.

            tien tran added a comment - I'm using bamboo version 6.3.1 build 60306, but still dont know what exact solution for it. What do we have to support this case if we marked this ticket resolved without any solution. What mentioned in this ticket's description is not truly a solution. The 1st way just only re-use stage idea, not a completely build plan template. The 2nd one is not entirely template, it required we clone a lot of build plan (manually) then replace them whenever we need. Still wait for update from bamboo team on this concern. Thank you.

            Try Bamboo 6.0 now.

            https://confluence.atlassian.com/display/BAMBOO/Bamboo+Specs

            Note that we do not have a full coverage of Bamboo features for now, but we'll get there.

            Przemek Bruski added a comment - Try Bamboo 6.0 now. https://confluence.atlassian.com/display/BAMBOO/Bamboo+Specs Note that we do not have a full coverage of Bamboo features for now, but we'll get there.

            Are there any news about this feature?

            Ihor Prokopiev added a comment - Are there any news about this feature?

            Pradeep added a comment -

            Just want to check when can we have this release?

            Pradeep added a comment - Just want to check when can we have this release?

            We have a similar situation. We're moving away from permanent cloud instances for certain sorts of testing and development to a more flexible approach.

            The new way of doing things is to create servers and whole mini-production environments with several different service machines. Scripting their creation and provisioning them is easy. Each of these services uses artifacts from any of several projects which we build using Bamboo. Currently we have to create deployment environments by hand for each machine that might for each applicable coding project. That wasn't a problem when the computing inventory was stable. Now that it's more volatile the whole thing cries out for automation. Bamboo will be a lot more useful to us when it supports automated creation and deprecation of these environments.

            Todd Ellner added a comment - We have a similar situation. We're moving away from permanent cloud instances for certain sorts of testing and development to a more flexible approach. The new way of doing things is to create servers and whole mini-production environments with several different service machines. Scripting their creation and provisioning them is easy. Each of these services uses artifacts from any of several projects which we build using Bamboo. Currently we have to create deployment environments by hand for each machine that might for each applicable coding project. That wasn't a problem when the computing inventory was stable. Now that it's more volatile the whole thing cries out for automation. Bamboo will be a lot more useful to us when it supports automated creation and deprecation of these environments.

            If you are disappointed, switch to Jenkins or TeamCity, they both have build plan templating.

            Terry Leung added a comment - If you are disappointed, switch to Jenkins or TeamCity, they both have build plan templating.

            Dawei Wang added a comment -

            This is disappointing.

            Dawei Wang added a comment - This is disappointing.

            DaveT added a comment -

            Following up on my previous comment: My company has over 50k employees and our division is the only one using Bamboo. The rest are using various tools, with Jenkins being the most common. We've been using Bamboo on our team since 2008 and have grown to three separate bamboo servers covering almost 8,000 build plans. We're not anxious to move to a different tool, but it seems like Atlassian's attention is focused elsewhere and Bamboo is rapidly joining the long list of "forgotten" applications that Atlassian maintains but never improves. We've decided to give Bamboo another 6 months, but if we're not seeing any movement we're prepared to move. With this many build plans, the lack of templates and the lack of any REST api to create build plans is quite a pain.

            DaveT added a comment - Following up on my previous comment: My company has over 50k employees and our division is the only one using Bamboo. The rest are using various tools, with Jenkins being the most common. We've been using Bamboo on our team since 2008 and have grown to three separate bamboo servers covering almost 8,000 build plans. We're not anxious to move to a different tool, but it seems like Atlassian's attention is focused elsewhere and Bamboo is rapidly joining the long list of "forgotten" applications that Atlassian maintains but never improves. We've decided to give Bamboo another 6 months, but if we're not seeing any movement we're prepared to move. With this many build plans, the lack of templates and the lack of any REST api to create build plans is quite a pain.

            Hi everyone,

            Build and deployment templates are now at the top of the backlog and one of our main priority for 2016. I agree with the feedback given here, templates will be a great asset to onboard people, introduce standards for configuration as well as help teams to manage large amounts of plans.

            We haven't been able to ship it yet as we focused this year on improving our Cloud experience and building better integrations with Docker and AWS. Tackling scale is going to be a greater focus area in the upcoming year. We know that addressing this particular request is going to be key to our success. As usual I cannot commit to any deadline but I can open up on the main priorities that we will be having.

            I'd like to take this opportunity to thank you for trusting us and for your patience. We really want to keep you happy and we will do our best to delight you even more in the upcoming months.

            Regards,

            Sten Pittet
            Senior Product Manager - Bamboo

            Sten Pittet (Inactive) added a comment - Hi everyone, Build and deployment templates are now at the top of the backlog and one of our main priority for 2016. I agree with the feedback given here, templates will be a great asset to onboard people, introduce standards for configuration as well as help teams to manage large amounts of plans. We haven't been able to ship it yet as we focused this year on improving our Cloud experience and building better integrations with Docker and AWS. Tackling scale is going to be a greater focus area in the upcoming year. We know that addressing this particular request is going to be key to our success. As usual I cannot commit to any deadline but I can open up on the main priorities that we will be having. I'd like to take this opportunity to thank you for trusting us and for your patience. We really want to keep you happy and we will do our best to delight you even more in the upcoming months. Regards, Sten Pittet Senior Product Manager - Bamboo

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

                Created:
                Updated:
                Resolved: