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

Trigger Deploy on Successful Unrelated Build

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Deployments, Triggers
    • None
    • 0
    • 2

    • 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've got a Build Plan that is doing some environment orchestration (e.g. restore database to previous state), and I'd love to be able to trigger a deployment to a specific environment on successful completion of this build. The deployment is associated with another build that produces deployable artifacts, so this orchestration build is technically unrelated to the Deployment Plan.

      The workflow would be as follows:

      1. On regular schedule, run orchestration build against QA1 environment to reset the environment
      2. If Build Plan fails stop processing
      3. If Build Plan succeeds, trigger deployment to QA1 environment

      If I configure the Deploy environment with the orchestration I am required to run the orchestration each time I want to deploy new artifacts, which is not always the case. Likewise, if I put the deployment in the Build Plan I lose release tracking of that environment provided from the Deploy management.

            [BAM-14946] Trigger Deploy on Successful Unrelated Build

            Sten Pittet (Inactive) added a comment -

            Hi Jason,

            Thanks for your feedback. I've linked this issue to BAM-13501 which is a similar request based on REST API triggers. We do not have plans yet to add support for this but it's something that we're likely to put on our radar in 2015.

            Thanks,

            Sten Pittet
            Bamboo Product Manager

            Sten Pittet (Inactive) added a comment - Hi Jason, Thanks for your feedback. I've linked this issue to BAM-13501 which is a similar request based on REST API triggers. We do not have plans yet to add support for this but it's something that we're likely to put on our radar in 2015. Thanks, Sten Pittet Bamboo Product Manager

              Unassigned Unassigned
              d1c790799271 Jason Schwanz
              Votes:
              2 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated: