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

Deployment projects don't start EC2 instances automatically

      I was able to reproduce the behavior when regular plans started EC2 instances and worked fine, but the deployment project stayed queued after passing the configured 1 minute threshold. See the attached screenshots.

      The deployment ran successfully after manually starting an elastic agent.

          Form Name

            [BAM-13588] Deployment projects don't start EC2 instances automatically

            At 'Mon Jul 28 23:35:40 EST 2014', actually. So they meant last Monday

            Robert Watkins added a comment - At 'Mon Jul 28 23:35:40 EST 2014', actually. So they meant last Monday

            Well, it hit my OD environment sometime overnight.

            Robert Watkins added a comment - Well, it hit my OD environment sometime overnight.

            Ops Team added a comment -

            Atlassian confirmed on Twitter that OnDemand is scheduled to receive 5.6 this coming Monday.

            https://twitter.com/atlassian/status/494222979325517824

            Ops Team added a comment - Atlassian confirmed on Twitter that OnDemand is scheduled to receive 5.6 this coming Monday. https://twitter.com/atlassian/status/494222979325517824

            Well, late July. But I can confirm that it does work.

            Robert Watkins added a comment - Well, late July. But I can confirm that it does work.

            This bug will be released with Bamboo 5.6 in early July.

            James Dumay added a comment - This bug will be released with Bamboo 5.6 in early July.

            @Tomasz Create a timed instance inside Bamboo instance image configuration and set it for every 15 minutes.
            This will check and ensure that you have a Deployment agent running every 15 minutes. If it shuts down due to timed termination of some sort, the check you create in bamboo will start another.

            Michael Dalzell added a comment - @Tomasz Create a timed instance inside Bamboo instance image configuration and set it for every 15 minutes. This will check and ensure that you have a Deployment agent running every 15 minutes. If it shuts down due to timed termination of some sort, the check you create in bamboo will start another.

            That is unfortunately a major bummer. Is there a know workaround? It there a way to use own servers for build and deployment purposes instead of EC2 instances? Anyone?

            Tomasz Rdzak added a comment - That is unfortunately a major bummer. Is there a know workaround? It there a way to use own servers for build and deployment purposes instead of EC2 instances? Anyone?

            The fix to this issue has been scheduled for 5.6

            Marcin Gardias added a comment - The fix to this issue has been scheduled for 5.6

            Deployment projects are a fundamental feature of Bamboo. I'm considering going back to just deploying software from build projects... why on earth was the entire concept of deployment projects put into production when it doesn't even work correctly?

            In 23 days this issue will be ONE YEAR old, with no updates except "oops, we closed the ticket". Complete fail on all fronts.

            jason.mitcheson added a comment - Deployment projects are a fundamental feature of Bamboo. I'm considering going back to just deploying software from build projects... why on earth was the entire concept of deployment projects put into production when it doesn't even work correctly? In 23 days this issue will be ONE YEAR old, with no updates except "oops, we closed the ticket". Complete fail on all fronts.

            Ops Team added a comment -

            Sad to see this is still an issue. Had to pull the plug on our implementation of AoD Bamboo because of it and the lack of deployment plan cloning.

            Ops Team added a comment - Sad to see this is still an issue. Had to pull the plug on our implementation of AoD Bamboo because of it and the lack of deployment plan cloning.

              mgardias Marcin Gardias
              akhachatryan ArmenA
              Affected customers:
              37 This affects my team
              Watchers:
              44 Start watching this issue

                Created:
                Updated:
                Resolved: