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

Deployment triggers should be ANDed together

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None
    • 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 only supports deploying (a) after a build completes or (b) following a certain schedule.

      What I would like to happen is let me set a schedule - say, 2:00 AM, but only if a new build is ready to go.

      I could just have my builds be scheduled, I suppose, but I'd prefer if it they were built after a commit, so that all the integration tests run while the humans are present. I could clone the build project and have one be scheduled and the other per-commit, but that is gross. I don't want to just re-deploy nightly unless there's a reason to.

            [BAM-15433] Deployment triggers should be ANDed together

            Sten Pittet (Inactive) added a comment -

            Hi jamesez,

            Thanks for your suggestion. We're already tracking down a similar requirement in BAM-14311. The goal would be to trigger scheduled deployments only when new changes are detected.

            I cannot give you a deadline for this deployment yet but this is something that we are aware of. As a workaround you could have a script at the beginning of your deployment that reads a file were you would have written the reference of the latest deployed artifact and fail the deployment if the artifact is the same. A variation of this code exists on answers.atlassian.com.

            Regards,

            Sten Pittet
            Bamboo Product Manager

            Sten Pittet (Inactive) added a comment - Hi jamesez , Thanks for your suggestion. We're already tracking down a similar requirement in BAM-14311 . The goal would be to trigger scheduled deployments only when new changes are detected. I cannot give you a deadline for this deployment yet but this is something that we are aware of. As a workaround you could have a script at the beginning of your deployment that reads a file were you would have written the reference of the latest deployed artifact and fail the deployment if the artifact is the same. A variation of this code exists on answers.atlassian.com . Regards, Sten Pittet Bamboo Product Manager

              Unassigned Unassigned
              ff498a03f956 Jim Zajkowski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: