• Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 4.0
    • None
    • 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.

      For folks with lots of projects - it'd be great to be able to create a Plan Template to be reused across each project; the only thing which changes is the SCM locations.

      e.g. for all the projects I work on, there maybe be 1-3 SCM locations (trunk & a few branches), then for each of them I want to have exactly the same plans - one for the CI and one for a nightly deploy in maven. So it'd be great if I could setup a 'Plan Template' to say this, then when creating a new project I can just refer to the plan template (which has each plan configuration inside it).

      It'd just save a fair bit of UI work on the end user - rather than having to create at least 2 plans manually for each SCM root, I could just basically add 1 project and list all the multiple SCM roots and pick a plan and I've just setup (say) 6 actual plans from one or two entry screens

            [BAM-907] plan templates to reuse across projects

            I don't think this Plan Branch is what was requested for originally... if you re-read the description it says template across different projects (e.g. project A , B and C). rather than branches within project A... can you re-open this ticket? It is such a pain to manage so many (100+) projects individually. For example, if I want to modify a value for a plug-in, I need to do this 100 times repeatedly! (Or spend time writing up a script to Bamboo REST). Either way it is a pain. What if we create a new project tomorrow and the plan owner didn't turn it on?? ARRGGGG

            This feature is long available in Jenkins and Team City but why not in Bamboo?? Is it because Bamboo is built for family use while other CI apps are built for enterprise use?

            Terry Leung added a comment - I don't think this Plan Branch is what was requested for originally... if you re-read the description it says template across different projects (e.g. project A , B and C). rather than branches within project A... can you re-open this ticket? It is such a pain to manage so many (100+) projects individually. For example, if I want to modify a value for a plug-in, I need to do this 100 times repeatedly! (Or spend time writing up a script to Bamboo REST). Either way it is a pain. What if we create a new project tomorrow and the plan owner didn't turn it on?? ARRGGGG This feature is long available in Jenkins and Team City but why not in Bamboo?? Is it because Bamboo is built for family use while other CI apps are built for enterprise use?

            James Dumay added a comment - - edited

            Hi all,

            This week we are introducing Plan branches as part of Bamboo 4.0.

            Plan Branches are a Bamboo Plan configuration that represent a branch in your version control system. They inherit all of the configuration defined by the parent Plan, except that instead of building against the repository's main line, they build against a specified branch. It is also worth noting that only users with edit access to the Plan can create Plan Branches that inherit from that plan.

            Watch for the release announcement on the Atlassian blog! If you have any questions or concerns feel free to comment on this ticket.

            Thanks
            James

            James Dumay added a comment - - edited Hi all, This week we are introducing Plan branches as part of Bamboo 4.0. Plan Branches are a Bamboo Plan configuration that represent a branch in your version control system. They inherit all of the configuration defined by the parent Plan, except that instead of building against the repository's main line, they build against a specified branch. It is also worth noting that only users with edit access to the Plan can create Plan Branches that inherit from that plan. Watch for the release announcement on the Atlassian blog ! If you have any questions or concerns feel free to comment on this ticket. Thanks James

            What I would need is to at least be able to alter the default template for project in such a way that the default permissions for a plan can be altered. I hate the fact that the default is to allow all logged in users access to a project. I don't want that.

            Arjan

            Deleted Account (Inactive) added a comment - What I would need is to at least be able to alter the default template for project in such a way that the default permissions for a plan can be altered. I hate the fact that the default is to allow all logged in users access to a project. I don't want that. Arjan

            There's a Project bulk copy plugin available that one of our Build Engineers wrote as a workaround for this very thing:

            https://plugins.atlassian.com/plugin/details/38700

            Hope that helps in the interim.

            Rene Medellin [Atlassian] added a comment - There's a Project bulk copy plugin available that one of our Build Engineers wrote as a workaround for this very thing: https://plugins.atlassian.com/plugin/details/38700 Hope that helps in the interim.

            This would be such a killer feature for my team. We have a plugin-based product where each plugin has its own repo. We have about ~20 plugins and growing. On top of that, we have two builds per plugin: Regular and Integration Test.

            So each release, our CM team needs to create 40 new build plans (1 per plugin, per branch, per build type). If by chance we fickle developers want to change how a Regular build is performed, our CM team has to make that change across all build plans which is insane. There should be a full build plan templating system with inheritance. I imagine we'd have the following templates:

            Regular Build Template

            • Plugin 1 Template
              • Plugin 1 Trunk Build Plan
              • Plugin 2 RB_5.0 Build Plan
                Integration Build Template
            • Plugin 1 Integration Template
              • Plugin 1 Trunk Build Plan
              • Plugin 2 RB_5.0 Build Plan

            Matt Hughes added a comment - This would be such a killer feature for my team. We have a plugin-based product where each plugin has its own repo. We have about ~20 plugins and growing. On top of that, we have two builds per plugin: Regular and Integration Test. So each release, our CM team needs to create 40 new build plans (1 per plugin, per branch, per build type). If by chance we fickle developers want to change how a Regular build is performed, our CM team has to make that change across all build plans which is insane. There should be a full build plan templating system with inheritance. I imagine we'd have the following templates: Regular Build Template Plugin 1 Template Plugin 1 Trunk Build Plan Plugin 2 RB_5.0 Build Plan Integration Build Template Plugin 1 Integration Template Plugin 1 Trunk Build Plan Plugin 2 RB_5.0 Build Plan

            While copying of plans is easy to do, I'd prefer plan templates as well.

            For instance we have a weekly 'build all reports' plan - across 20 projects.
            If we change our central buildfiles to generate another report, we'd have to change 20 artifact-pages, which is quite annoying.
            Also this would come in handy, if the quite periods of normal plans are to low and the build queues are filled to fast. Just editing the plan template and increase the quite period.

            When creating a template Plan, all I'd need was an extra page to specify which variables the plan refers (say 'CVS Module to build').
            When creating an instance of that template plan Bamboo just had to ask for the content of that variable name.

            If you want to be more sophisticated of course in an instance you were allowed to explicitely overwrite each default-value.

            Stefan Hansel added a comment - While copying of plans is easy to do, I'd prefer plan templates as well. For instance we have a weekly 'build all reports' plan - across 20 projects. If we change our central buildfiles to generate another report, we'd have to change 20 artifact-pages, which is quite annoying. Also this would come in handy, if the quite periods of normal plans are to low and the build queues are filled to fast. Just editing the plan template and increase the quite period. When creating a template Plan, all I'd need was an extra page to specify which variables the plan refers (say 'CVS Module to build'). When creating an instance of that template plan Bamboo just had to ask for the content of that variable name. If you want to be more sophisticated of course in an instance you were allowed to explicitely overwrite each default-value.

              Unassigned Unassigned
              3af585c36b47 James Strachan
              Votes:
              9 Vote for this issue
              Watchers:
              12 Start watching this issue

                Created:
                Updated:
                Resolved: