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

Plan configuration change control and versioning



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


      I would like one or more methods to help document and understand how the build plans change over time. A change to a build plan can have major ramifications to the result produced by the build so it is important to understand and document changes to the plan. For example, our prior build processes, the build process was controlled by scripts that were themselves in source control and therefore had a version history. There are various levels of support that would help in this regard:

      1. Add a comment field when a plan configuration is saved so that change can be documented
      2. Provide automatic versioning of plans (like Confluence page versioning for instance) where differences between versions could be highlighted
      3. Provide a text representation of the plan that can be imported/exported to source control
        • Perhaps even a configuration so that plan changes are automatically put into source control
      4. Optionally require a JIRA issue to be associated with any plan change


        Issue Links



              Unassigned Unassigned
              bob.swift Bob Swift
              53 Vote for this issue
              35 Start watching this issue