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

Allow specification of "manual-ness" of stage per branch plan


    • Icon: Suggestion Suggestion
    • Resolution: Tracked Elsewhere
    • None
    • Plan Branches, Stages
    • None
    • 0
    • 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.

      I may already have a workaround for this, but the intent here is around a workflow where artifacts are published to a central repository, in this case Maven;

      The primary plan runs against the development line and drops -SNAPSHOT builds to maven, and should automatically do so; however, a release branch should have the mvn deploy call be a manual step to allow for review.

      Another example of where this would be useful is for situations where a development build publishes to a development server, but a production build should pause before deployment to the production server - deployment location is parameterized to allow variation in the final location.

            Unassigned Unassigned
            4c7f42da203a John Knight
            1 Vote for this issue
            3 Start watching this issue