• 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

            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 1442979 ] New: JAC Bug Workflow v3 [ 3383619 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Bamboo Workflow 2016 v1 [ 1420715 ] New: Bamboo Workflow 2016 v1 - Restricted [ 1442979 ]
            Marek Went (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2014 v2 [ 961848 ] New: Bamboo Workflow 2016 v1 [ 1420715 ]
            Marcin Oles made changes -
            Resolution New: Answered [ 9 ]
            Status Original: Needs Triage [ 10030 ] New: Resolved [ 5 ]
            Bill Langton made changes -
            Priority Original: Minor [ 4 ] New: Critical [ 2 ]
            Bill Langton created issue -

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

                Created:
                Updated:
                Resolved: