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

Change default (from bamboo deployments) of "Releases from branches will default to using the branch name suffixed with the build number of the build result"

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Done
    • 6.1.0
    • Deployments
    • 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.

      Would be extremely helpful and just plain logical for the "Release Version" to apply for all branches of a particular build plan.

      We release from different release branches (with the JIRA ticket integration e.g. release-XPROJ-1, release-XPROJ-2).

      It seems that Bamboo deployments was created with the mindset there would only be a single release branch...would that be correct?

            [BAM-14355] Change default (from bamboo deployments) of "Releases from branches will default to using the branch name suffixed with the build number of the build result"

            Marcin Gardias added a comment - - edited

            Requested option will be added in Bamboo 6.1.

            Marcin Gardias added a comment - - edited Requested option will be added in Bamboo 6.1.

            Ed Silva added a comment -

            This blocks us from creating auto-releases, since we need to edit the artifacts release name. It has been two months and no word from developers ?

            Ed Silva added a comment - This blocks us from creating auto-releases, since we need to edit the artifacts release name. It has been two months and no word from developers ?

            Rich Duncan added a comment -

            We really need the ability to do variable based release versioning when deploying from a branch. We are using the same branching strategy as the Bitbucket team as documented here which requires us to release out of a branch. This would enable us to define the main portion of the release in a plan variable and over-ride that and the incremental variable in each plan branch.

            Rich Duncan added a comment - We really need the ability to do variable based release versioning when deploying from a branch. We are using the same branching strategy as the Bitbucket team as documented here which requires us to release out of a branch. This would enable us to define the main portion of the release in a plan variable and over-ride that and the incremental variable in each plan branch.

            Deleted Account (Inactive) added a comment -

            A plugin for now would be good. It's getting a bit messy now managing the deployments because of this limitation.

            Deleted Account (Inactive) added a comment - A plugin for now would be good. It's getting a bit messy now managing the deployments because of this limitation.

            Arik Kfir added a comment -

            We're heavy users of Bamboo here @ Infolinks - and this is our #1 requested feature.

            Arik Kfir added a comment - We're heavy users of Bamboo here @ Infolinks - and this is our #1 requested feature.

            Deleted Account (Inactive) added a comment -

            Still no update on this?

            Deleted Account (Inactive) added a comment - Still no update on this?

            Deleted Account (Inactive) added a comment -

            Same case in my current project. It will be great if this functionality will be implemented, especially for Agile development.

            Any workaround or plugins?

            Deleted Account (Inactive) added a comment - Same case in my current project. It will be great if this functionality will be implemented, especially for Agile development. Any workaround or plugins?

            Ron Chan added a comment -

            Not exactly a duplicate.

            https://jira.atlassian.com/browse/BAM-14422 goes hand in hand with this, in that it's functionality on the JIRA side when the "Release version" is clicked. Though not entirely certain but fixing the Bamboo request may address the JIRA one.

            Ron Chan added a comment - Not exactly a duplicate. https://jira.atlassian.com/browse/BAM-14422 goes hand in hand with this, in that it's functionality on the JIRA side when the "Release version" is clicked. Though not entirely certain but fixing the Bamboo request may address the JIRA one.

            Etan Reisner added a comment -

            Duplicate of https://jira.atlassian.com/browse/BAM-14422?

            Etan Reisner added a comment - Duplicate of https://jira.atlassian.com/browse/BAM-14422?

            Paul Kelcey (Inactive) added a comment -

            Hi,

            Thank you for raising this. We have accepted this onto the backlog and we will be considering solutions for this when we next have the hood up on deployments. That may be a little way off at the moment unfortunately (e.g. six to twelve months) due to other priorities but we'll definitely be including this in the mix when we do.

            Regards,

            Paul Kelcey
            Bamboo Development Manager

            Paul Kelcey (Inactive) added a comment - Hi, Thank you for raising this. We have accepted this onto the backlog and we will be considering solutions for this when we next have the hood up on deployments. That may be a little way off at the moment unfortunately (e.g. six to twelve months) due to other priorities but we'll definitely be including this in the mix when we do. Regards, Paul Kelcey Bamboo Development Manager

              mgardias Marcin Gardias
              a926d21adf42 Ron Chan
              Votes:
              11 Vote for this issue
              Watchers:
              13 Start watching this issue

                Created:
                Updated:
                Resolved: