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

Scheduled deployments should only run if the latest version is different than what is actually deployed in that environment

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 9.0.0
    • None
    • Deployments, Triggers
    • None

      Say there is a deployment environment with a Scheduled trigger to run once an hour. Version 1.0 is currently deployed. When the trigger executes, if Version 1.0 is the latest available version, it shouldn't actually execute the deployment because it is just redeploying the same thing that is already deployed in the environment.

      Having a an checkbox option to enable this would be desirable ("Don't deploy if latest version matches version currently deployed").

            [BAM-14311] Scheduled deployments should only run if the latest version is different than what is actually deployed in that environment

            Freeman, Jade added a comment -

            +1

            Freeman, Jade added a comment - +1

            Oskari Jokinen added a comment -

            +1

            Oskari Jokinen added a comment - +1

            thirdlight added a comment -

            +1

            How was this even released? It's clearly a stupid piece of behaviour, with presumably a pretty simple fix. But you know - a 5 year old bug with a mere 27 votes. Why am I even bothering...

            thirdlight added a comment - +1 How was this even released? It's clearly a stupid piece of behaviour, with presumably a pretty simple fix. But you know - a 5 year old bug with a mere 27 votes. Why am I even bothering...

            David Paquin added a comment -

            +1

            David Paquin added a comment - +1

            Igor Gleyzer added a comment -

            +1

            Igor Gleyzer added a comment - +1

            Edward Burns added a comment - - edited

            Agree with Chris Cooper. Why would anyone want to increment the version number and deploy if there are no changes? This is a 5 year old bug!! Fix It

            Edward Burns added a comment - - edited Agree with Chris Cooper. Why would anyone want to increment the version number and deploy if there are no changes? This is a 5 year old bug!! Fix It

            Pieter Wouter Hartog added a comment -

            +1

            Yes, this is causing issues in our environment: if we re-deploy existing releases it is causing errors and other issues. Only deploy if there is something new.

            Pieter Wouter Hartog added a comment - +1 Yes, this is causing issues in our environment: if we re-deploy existing releases it is causing errors and other issues. Only deploy if there is something new.

            Chris Cooper added a comment -

            This really should have been there on day 1. Why would anyone want to increment the version number and deploy if there are no changes?

            Chris Cooper added a comment - This really should have been there on day 1. Why would anyone want to increment the version number and deploy if there are no changes?

            Frederik added a comment -

            +1

            In our case a deployment uploads the build to a beta version distribution system which subsequently triggers email alerts to a bunch of beta testers. We’d like to do automated nightly releases, but since the project is not being worked on every day using a scheduled deployment trigger in Bamboo would result in a lot of identical builds being distributed to the beta testers.

            Frederik added a comment - +1 In our case a deployment uploads the build to a beta version distribution system which subsequently triggers email alerts to a bunch of beta testers. We’d like to do automated nightly releases, but since the project is not being worked on every day using a scheduled deployment trigger in Bamboo would result in a lot of identical builds being distributed to the beta testers.

            Jason Schwanz added a comment -

            I would definitely love to have this feature. As it is now, it will create a new Version 1.0 (named something like Version 1.0_1). This seems like a big oversight to me.

            Jason Schwanz added a comment - I would definitely love to have this feature. As it is now, it will create a new Version 1.0 (named something like Version 1.0_1). This seems like a big oversight to me.

              mgardias Marcin Gardias
              127970255624 David Ehringer
              Affected customers:
              34 This affects my team
              Watchers:
              28 Start watching this issue

                Created:
                Updated:
                Resolved: