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

Deployment trigger scheduler should have option to not deploy the same code

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • 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 an option on the deployment plan's scheduler to not trigger a deployment if there has been no new code updates to the parent plan.

      Current world, if I set up a cron trigger to deploy hourly from FOO-BAR build plan, it will continue to deploy every hour even if there is no change to FOO-BAR. (Essentially, deploying FOO-BAR-12 artifact over and over and over)

      I see how this may be desirable for some users, but our use case for this improvement is that a deployment to our QA environment leads to about 5 mins of downtime as the servers all re-initialize. We want to only incur that cost if there is something new to deploy, and know through cron that it will only happen at most on the hour every hour.

            [BAM-14916] Deployment trigger scheduler should have option to not deploy the same code

            Jon Stalnaker added a comment -

            I'd like to see this feature implemented as well.

            Jon Stalnaker added a comment - I'd like to see this feature implemented as well.

            Sten Pittet (Inactive) added a comment -

            Hi Eric,

            At this stage the best workaround that I see is in Answers but it seems that you are already aware of it.

            We have improvements for deployments in our backlog but the development should not start before the end of the year.

            Cheers,

            Sten

            Sten Pittet (Inactive) added a comment - Hi Eric, At this stage the best workaround that I see is in Answers but it seems that you are already aware of it. We have improvements for deployments in our backlog but the development should not start before the end of the year. Cheers, Sten

            Eric Fusciardi added a comment -

            We've thought about that but every way we have implemented just "fails" the build, which is an undesirable state to leave the deploy plan in.

            Can you suggest a way to "stop" the deploy which will leave the state of it on the dpeloy dashboard as "Green" from the last real deploy?

            Eric Fusciardi added a comment - We've thought about that but every way we have implemented just "fails" the build, which is an undesirable state to leave the deploy plan in. Can you suggest a way to "stop" the deploy which will leave the state of it on the dpeloy dashboard as "Green" from the last real deploy?

            Sten Pittet (Inactive) added a comment -

            Hi Eric,

            Thanks for your suggestion, it would be interesting indeed to prevent deployments from happening if the code hasn't change. I cannot give you a concrete deadline for this development due to the current priorities but this is something that we may look at at the beginning of the next year.

            As a workaround you could script a task that would check whether the version of the build has changed and stop the deployment if it's not the case.

            Cheers,

            Sten Pittet
            Bamboo Product Manager

            Sten Pittet (Inactive) added a comment - Hi Eric, Thanks for your suggestion, it would be interesting indeed to prevent deployments from happening if the code hasn't change. I cannot give you a concrete deadline for this development due to the current priorities but this is something that we may look at at the beginning of the next year. As a workaround you could script a task that would check whether the version of the build has changed and stop the deployment if it's not the case. Cheers, Sten Pittet Bamboo Product Manager

              Unassigned Unassigned
              e3b50d08b0c3 Eric Fusciardi
              Votes:
              1 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: