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

      We use bamboo for critical operations, like releasing, deploy in production, etc. Each one has a corresponding stage. It would be nice if bamboo had a more fine grained security, so that a project lead, for example, is allowed to trigger release stage while a developer isn't.

            [BAM-9613] Have stage permissions

            I don't believe this has been resolved, as the issue is with having permissions around stages. As per Deepu's comments. is there anyway you can look at this again?

            Deleted Account (Inactive) added a comment - I don't believe this has been resolved, as the issue is with having permissions around stages. As per Deepu's comments. is there anyway you can look at this again?

            Deployment projects feature is great , but I still like the simple "Stage permission" option . There is lots of use cases where it will be useful .

            Like do a maven release ( not any prod deploys) and only team leads can do that .

            Deepu Mathew added a comment - Deployment projects feature is great , but I still like the simple "Stage permission" option . There is lots of use cases where it will be useful . Like do a maven release ( not any prod deploys) and only team leads can do that .

            This is outstanding news James. I told a lot of our managers and other developers about this new QA component you guys are adding into Bamboo and they were very excited about it.

            This will hopefully make our process much less kludgey when it comes to authorizing builds through our QA department.

            I am already working on getting an update plan to test this out and to look out re-writing our process plans for releasing builds

            Cameron Ferguson added a comment - This is outstanding news James. I told a lot of our managers and other developers about this new QA component you guys are adding into Bamboo and they were very excited about it. This will hopefully make our process much less kludgey when it comes to authorizing builds through our QA department. I am already working on getting an update plan to test this out and to look out re-writing our process plans for releasing builds

            Very soon, Cameron

            James Dumay added a comment - Very soon, Cameron

            Any idea on when 5.0 is set to release? Next month? later this year? 2014?

            Cameron Ferguson added a comment - Any idea on when 5.0 is set to release? Next month? later this year? 2014?

            Great news James! I'm excited to check this release.

            Ricardo Mayerhofer added a comment - Great news James! I'm excited to check this release.

            James Dumay added a comment - - edited

            Hi there,

            We have built a new concept in Bamboo called Deployment Projects that makes deployment a first class practice inside of Bamboo. Deployment projects provide a first class representation of environments and related deployable software versions.

            After reviewing many tickets involving the use of stages for controling deployment processes, the Bamboo team at Atlassian have decided that we will not be implementing this feature in its suggested form.

            In order to keep our Continuous Integration workflow pure and uncluttered, deployment projects exist alongside Bamboo build projects and plans.

            Deployment projects replace the need for:

            Deployment projects in their current form:

            • Provide reporting to what software versions are running on any given environment, including a full release report of issues and commits that have made up that version.
            • Have flexible permissions. For example, it's possible to completely lock down your production environment so that only members of a particular group can deploy to it while allowing QA to deploy to their own Staging or QA environment
            • Do not enforce a rigid pipeline structure, so that any testing environments can be "skipped" if the need arises.
            • Have built-in support for rollbacks.

            Deployment projects will be making their debut in Bamboo 5.0. This release will be made available for free for customers who hold an active license.

            If you have any questions, please do not hesitate to email me at james@atlassian.com or leave a comment below.

            Thanks,
            James Dumay
            Bamboo Product Manager

            James Dumay added a comment - - edited Hi there, We have built a new concept in Bamboo called Deployment Projects that makes deployment a first class practice inside of Bamboo. Deployment projects provide a first class representation of environments and related deployable software versions. After reviewing many tickets involving the use of stages for controling deployment processes, the Bamboo team at Atlassian have decided that we will not be implementing this feature in its suggested form. In order to keep our Continuous Integration workflow pure and uncluttered, deployment projects exist alongside Bamboo build projects and plans. Deployment projects replace the need for: Skipping stages to avoid deploying to testing environments Permissions for stages to control who can deploy Re-running successful stages for rollbacks Deployment projects in their current form: Provide reporting to what software versions are running on any given environment, including a full release report of issues and commits that have made up that version. Have flexible permissions. For example, it's possible to completely lock down your production environment so that only members of a particular group can deploy to it while allowing QA to deploy to their own Staging or QA environment Do not enforce a rigid pipeline structure, so that any testing environments can be "skipped" if the need arises. Have built-in support for rollbacks. Deployment projects will be making their debut in Bamboo 5.0. This release will be made available for free for customers who hold an active license. If you have any questions, please do not hesitate to email me at james@atlassian.com or leave a comment below. Thanks, James Dumay Bamboo Product Manager

            We would also love to have this feature +1

            Alex Barnes added a comment - We would also love to have this feature +1

            Vote +1 for me.

            We would want to use this for deploy also, and confine the "deploy" trigger to select people, in charge of a given testing or deployment stage.

            Tyler Mace added a comment - Vote +1 for me. We would want to use this for deploy also, and confine the "deploy" trigger to select people, in charge of a given testing or deployment stage.

            what is the work around for this atm? so this is what I need

            I curently have a bamboo plan with stages setup like so

            1. build and test
            2. deploy snapshot
            3. deploy to dev(manual)... (i would like to allow user A,B,C to deploy)
            4. deploy to qa(manual)... (i would like to allow user B,C to deploy)
            5. deploy to prod(manual)... (i would like to allow user C to deploy)

            How can I setup the job so only certain users who have permission are allowed to deploy to dev, deploy to qa and deploy to prod.. Also I need it so each previous stage must be performed before the next.

            If stages had permissions then this would be easy but that is still under development. Can I make it so stages 3,4,5 are also plans and that the parent plans that must succeed beforehand? is there a plugin that can take a password to allow execution?

            Rafael Mahnovetskty added a comment - what is the work around for this atm? so this is what I need I curently have a bamboo plan with stages setup like so 1. build and test 2. deploy snapshot 3. deploy to dev(manual)... (i would like to allow user A,B,C to deploy) 4. deploy to qa(manual)... (i would like to allow user B,C to deploy) 5. deploy to prod(manual)... (i would like to allow user C to deploy) How can I setup the job so only certain users who have permission are allowed to deploy to dev, deploy to qa and deploy to prod.. Also I need it so each previous stage must be performed before the next. If stages had permissions then this would be easy but that is still under development. Can I make it so stages 3,4,5 are also plans and that the parent plans that must succeed beforehand? is there a plugin that can take a password to allow execution?

              Unassigned Unassigned
              9108eb612d82 Ricardo Mayerhofer
              Votes:
              46 Vote for this issue
              Watchers:
              25 Start watching this issue

                Created:
                Updated:
                Resolved: