• Icon: Bug Bug
    • Resolution: Answered
    • Icon: High High
    • None
    • None
    • None
    • None

      An update that was pushed out a week ago has broken our Bamboo build and deploy process. It worked fine on Friday. Attempted update on Sunday. No longer works on Monday. We are using OnDemand.

      I posted on the forums last week but no responses so far.

      https://answers.atlassian.com/questions/30949489/elastic-bamboo-error---failed-on-updating-stock-images

      The java error is in the forum post.

      We are using a custom 64bit windows server 2008 image. Java 8 is the only Java installed.

      It appears that the Deploy Artifacts are being zipped differently and our deployment packages are incomplete/unusable. I have attached screenshots of how the artifacts appear to be different.

        1. Last Friday Sept 25 2015.PNG
          Last Friday Sept 25 2015.PNG
          104 kB
        2. Now.png
          Now.png
          189 kB

            [BAM-16415] failed on updating stock image

            Contacted support. The Deployment Bundle is operational again so it appears they have restarted our instance. Thanks.

            Bill Langton added a comment - Contacted support. The Deployment Bundle is operational again so it appears they have restarted our instance. Thanks.

            Bill, please contact support, tell them you're affected by the artifact bug from the last week. They will restart your instance and the artifacts will be correctly created.
            The stock image error is unrelated.

            Przemek Bruski added a comment - Bill, please contact support, tell them you're affected by the artifact bug from the last week. They will restart your instance and the artifacts will be correctly created. The stock image error is unrelated.

            It's critical to me. We can't deploy and test or push to prod.

            Bill Langton added a comment - It's critical to me. We can't deploy and test or push to prod.

              Unassigned Unassigned
              0ea1566144fc Bill Langton
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: