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

Ability to add plan, via REST API or from XML config file.

    • 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.

      Currently, adding a plan is a very tedious process - some one has to click through the setup wizard to add a new plan and there is no other alternative.

      We should just be able to point to a XML file and add multiple plans based on XML configuration,

      For instance, adding ~100 plans becomes very laborious and can take several hours.

            [BAM-2630] Ability to add plan, via REST API or from XML config file.

            Without a general rest call into bamboo plan creation has lead to significant bottlenecks into our operation. We will probably drop bamboo as a result and move to jenkins.

            Charles Scott added a comment - Without a general rest call into bamboo plan creation has lead to significant bottlenecks into our operation. We will probably drop bamboo as a result and move to jenkins.

            This is duplicated by BAM-4854

            James Dumay added a comment - This is duplicated by BAM-4854

            I can not see a method in the examples to add a new plan in the CLI tool. There are options to clone an existing plan, but this is not quite the same as what is being requested.

            Adam Downer added a comment - I can not see a method in the examples to add a new plan in the CLI tool. There are options to clone an existing plan, but this is not quite the same as what is being requested.

            The bamboo CLI has some examples of how to do all these tasks. It's not a REST api, but it still feeds quite well into automation.

            See https://marketplace.atlassian.com/plugins/org.swift.atlassian.cli, examples/bamboo-* in the zip.

            It's worth pointing out that the atlassian CLI tools can do tons of stuff that is not exposed in their API. I can only presume they're hitting beans over JNI or something.

            Andrew Kesterson added a comment - The bamboo CLI has some examples of how to do all these tasks. It's not a REST api, but it still feeds quite well into automation. See https://marketplace.atlassian.com/plugins/org.swift.atlassian.cli , examples/bamboo-* in the zip. It's worth pointing out that the atlassian CLI tools can do tons of stuff that is not exposed in their API. I can only presume they're hitting beans over JNI or something.

            I heard it's possible to export xml data for a build plan. Why would I export something if I have no ability to import it? Perhaps I do not understand the value of such an export?

            Charles Scott added a comment - I heard it's possible to export xml data for a build plan. Why would I export something if I have no ability to import it? Perhaps I do not understand the value of such an export?

            This is also very important to us and is the primary show stopper from adding Bamboo to our Atlassian products set (Jira, Confluence).

            We have various Projets with lots of single maven builds. Due to the huge number of build to create on each branch, tag, etc, we automated that in Continuum with their supplied API.

            Looking now at switching to Bamboo, but the inability to remotely create hundreds of plan programmability is blocking us. We can't afford to create 500-1000 plan manually. Some sort of integrated API or a communication plug-in would be greatly appreciate.

            Philippe Busque added a comment - This is also very important to us and is the primary show stopper from adding Bamboo to our Atlassian products set (Jira, Confluence). We have various Projets with lots of single maven builds. Due to the huge number of build to create on each branch, tag, etc, we automated that in Continuum with their supplied API. Looking now at switching to Bamboo, but the inability to remotely create hundreds of plan programmability is blocking us. We can't afford to create 500-1000 plan manually. Some sort of integrated API or a communication plug-in would be greatly appreciate.

            EddieW added a comment -

            Agreed, this is very important to us. Our company uses several of Atlassian's tools to build-out an entire project platform (wiki, issue tracker, source review and Continous integration server) for any user on request, in an automated fashion (i.e. Google Code).

            Jira and Confluence make the process incredibly easy through their SOAP API, but Fisheye and Bamboo require our admin team to respond to each request and manually setup the new project in those tools.

            BTW Bamboo 3 is amazing!

            EddieW added a comment - Agreed, this is very important to us. Our company uses several of Atlassian's tools to build-out an entire project platform (wiki, issue tracker, source review and Continous integration server) for any user on request, in an automated fashion (i.e. Google Code). Jira and Confluence make the process incredibly easy through their SOAP API, but Fisheye and Bamboo require our admin team to respond to each request and manually setup the new project in those tools. BTW Bamboo 3 is amazing!

            Bernd Haug added a comment -

            A documented facility for programmatically creating/configuring both plans and the projects to put them in would be greatly appreciated.

            We develop our internal library in very fine-grained artifacts and having a facility that lets programmers create their own projects would be great for productivity, and for delivering nimbler products:

            As is, it's too complicated to have a separate project for each separate functionality, so the end result is huge utility libraries that will be copied into the final output archives, which is less than desirable.

            A well-documented and scriptable interface utility to run locally with the Bamboo instance (as, I think, requested in BAM-3112) would be nice as a start, but having such a feature in the remote API would be really great!

            Bernd Haug added a comment - A documented facility for programmatically creating/configuring both plans and the projects to put them in would be greatly appreciated. We develop our internal library in very fine-grained artifacts and having a facility that lets programmers create their own projects would be great for productivity, and for delivering nimbler products: As is, it's too complicated to have a separate project for each separate functionality, so the end result is huge utility libraries that will be copied into the final output archives, which is less than desirable. A well-documented and scriptable interface utility to run locally with the Bamboo instance (as, I think, requested in BAM-3112 ) would be nice as a start, but having such a feature in the remote API would be really great!

              Unassigned Unassigned
              57d5d3278d0f Lloyd Chang
              Votes:
              37 Vote for this issue
              Watchers:
              26 Start watching this issue

                Created:
                Updated:
                Resolved: