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

Storing Build Repositories in Repository



    • Suggestion
    • Resolution: Duplicate
    • None
    • 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.


      Consider a very large codebase, more than 10 years old. Currently supported versions consist of code written in Visual Studio 2010, Visual Studio 2012 and Visual Studio 2013. Chances are the next version is going to support Visual Studio 2015.

      Now consider that the repo has numerous branches, e.g. release-v4.5, release-v5.0, release-v5.1, release-v5.5, release-v6.0, release-v6.1, develop and master. Each branch has its own set of dependencies, in terms of Visual Studio, Platforms and Architectures (e.g. 32bit vs 64bit).

      Also consider that keeping this in Bamboo complicates configuration, is time consuming, error prone and doesn't allow for use of features (like build all branches).

      Allow for the plan configuration to be stored in the repo, so that it can be versioned with each branch. When the repo changes, read the plan configuration (aka capabilities, steps) from the repo in order to execute it.

      So the net effect is that Bamboo can still use the right agent to build the system based on its capabilities, while easing configuration by being able to build "all" branches. While the master branch may be using Visual Studio 2015, while release-v5.5 can still use Visual Studio 2012.


        Issue Links



              Unassigned Unassigned
              bcd96b272979 bloudraak
              0 Vote for this issue
              2 Start watching this issue