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

Create distinct permission for Manual Stages in a build pipeline.

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Build Queues, Stages
    • 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.

      Bamboo currently provides 5 basic permissions that can be applied on a per-plan basis:

      • View
      • Edit
      • build
      • Clone
      • Admin

      We have the need for a sixth:

      • Pass Manual Stages

      And Ideally this would be a per-stage permission

      We use manual stages for deployment and verification steps. However our organization enforces strict segregation of duties, so a Developer may never deploy to non-dev environments. That is why we would like to add our deployment team's group to specific manual stages.

      This would give us the future flow of:

      1. Stage 1 (build, test and tag)
        1. Developer releases current version from Jira
        2. Release invokes a build in Bamboo
          1. Checkout latest
          2. Run unit and acceptance tests
          3. Report on code coverage, findbugs, pmd
          4. Tag JIra version (1.2.2-SNAPSHOT) in VCS
      2. Stage 2 - Manual (deploy to Dev)
        1. Execute deployment scripts (Developers or Deployers only)
      3. Stage 3 - Manual (deploy to Test or Performance)
        1. Execute deployment scripts (Deployers only)

            Unassigned Unassigned
            3a10b11ad777 EddieW
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: