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

Allow customers to visually select a plan branch in the artifact downloader

XMLWordPrintable

    • 0
    • 1

    • 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 when selecting a plan to download an artifact from customers do not have a view of the plan branches. It appears that if the branch creates an artifact of the same name as the master (or another branch) the task downloads the most recent artifact.

      Customers would like the ability to visually select the specific branch the artifact is pulled from in order to avoid any confusion/mistakes when downloading artifacts.

      Currently the dropdown looks like this:

      It would be great if each plan could possibly have a further dropdown showing its branches or even just making the plan branches searchable/useable in that list.

        1. screenshot.png
          78 kB
          Carlen Benard

            [BAM-14745] Allow customers to visually select a plan branch in the artifact downloader

            Heena Agrawal added a comment -

            Sharing artifacts between branches under the same build plan would be very useful. Currently we have to manage multiple build plans to support this functionality. 

            Heena Agrawal added a comment - Sharing artifacts between branches under the same build plan would be very useful. Currently we have to manage multiple build plans to support this functionality. 

            Alexey K added a comment -

            This is very needed for deployment plans. It's often that a deployment plan combines a platform out of different components that are not synchronized by branch names. For example my super-enterprise-platform consists of:
            core v.3
            api v.7
            synchronization v.2

            Those all are different repos and different branch names. And now it's simply impossible to implement a nice deployment plan for this case. The only workaround is to manually (by task in build plan) sort out artifacts in some share folder outside of bamboo. That is very inconvenient.

            Alexey K added a comment - This is very needed for deployment plans. It's often that a deployment plan combines a platform out of different components that are not synchronized by branch names. For example my super-enterprise-platform consists of: core v.3 api v.7 synchronization v.2 Those all are different repos and different branch names. And now it's simply impossible to implement a nice deployment plan for this case. The only workaround is to manually (by task in build plan) sort out artifacts in some share folder outside of bamboo. That is very inconvenient.

            Radek Antoniuk added a comment -

            This would be definitely useful!
            Otherwise, we need to have separate build plans to be able to select specific branch artifact.

            Radek Antoniuk added a comment - This would be definitely useful! Otherwise, we need to have separate build plans to be able to select specific branch artifact.

              Unassigned Unassigned
              cbenard Carlen Benard (Inactive)
              Votes:
              9 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: