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

Cloned deployment project should take value from the latest configuration instead of the snapshot of the previous project

XMLWordPrintable

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

      Summary

      As pointed out by the title itself, a cloned deployment project currently still takes the snapshot (thus together with the previous project configurations) of the previous deployment project configurations into consideration.

      If you try to run this cloned deployment project, the build will fail because it is using the definitions of the previous deployment project. To fix this, you need to make a new release, only then the cloned deployment project will use the current project settings.

      Ideally, the cloned project should immediately take the latest settings instead of having to create a new release first.

              Unassigned Unassigned
              vchin Vincent Chin (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: