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

Trigger for deployments on build stage completion

XMLWordPrintable

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

      I would like to be able to trigger a deployment to a particular environment once one of my stages has been completed.

      My goal is to create different deploy environments, each with separate permissions, some tied to fully automated build plan stages and others tied to manual stages of the same build plan.

      I can see a few reasons for this:

      1. You want to isolate the 'deployment' tasks from the 'build' tasks. If my deployment to prod fails due to, say, a connectivity issue, that doesn't mean I need to rebuild my binary. Just re-running a deployment should be fine.
      2. Tag creation and artifact promotion (to name 2) do not belong to deployment. I want to be able to re-run my deployments, roll them back, etc. How should I address the tag creation if I put this task in a deployment environment? Think of re-running deployments, roll-backs, etc.
      3. I still want to have as much as possible automated, hence I want to deploy to my ENV: Test as soon as I have a green build. I do not want my developers to have to manually create and deploy a release.

      Found the following related tickets:

      BAM-13347 - Represent deployment triggers as stages within a plan OPEN
      BAM-13501 - Authenticate to see issue details

      And also logged this question in Atlassian answers:
      https://answers.atlassian.com/questions/11441200/bamboo-deployment-how-to-trigger-it-without-completing-all-stages

            [BAM-16160] Trigger for deployments on build stage completion

            Steffen Opel [Utoolity] added a comment -

             The After successful stage trigger for deployment environments is available meanwhile (I think as of Bamboo 5.10):

            Starts a deployment after a successful build of the specified stage of a plan. If there is only one existing stage, it is selected by default.

            Steffen Opel [Utoolity] added a comment -  The After successful stage trigger for deployment environments is available meanwhile (I think as of Bamboo 5.10): Starts a deployment after a successful build of the specified stage of a plan. If there is only one existing stage, it is selected by default.

            mark_gillespie added a comment -

            We have a manual stage, which JIRA use to release from JIRA ("release using existing build"), this requires a manual stage.

            Out manual stage does nothing more than check out the GIT revision of the repository and tags it with the Release Number, and then pushes the tag,

            because we use a manual stage, our Bamboo deployments don't trigger automatically at present

            mark_gillespie added a comment - We have a manual stage, which JIRA use to release from JIRA ("release using existing build"), this requires a manual stage. Out manual stage does nothing more than check out the GIT revision of the repository and tags it with the Release Number, and then pushes the tag, because we use a manual stage, our Bamboo deployments don't trigger automatically at present

              Unassigned Unassigned
              xabierdavila Xabier Davila
              Votes:
              12 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: