Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-12759

Archiving failure should make build fail (or unstable)

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major Major
    • core
    • None

      If archiving fails, i.e., the console log ends as follows (as for example seen in the description of JENKINS-7038):

      [snip Ant-based build...]
      BUILD SUCCESSFUL
      Total time: 4 seconds
      [snip...]
      Archiving artifacts
      ERROR: Failed to archive artifacts: 
      [snip stack trace related to some connection failure in publish-over-CIFS code...]
      Finished: SUCCESS
      

      then Jenkins (1.409.1 which we used back then) decides this a successful build. However, since only part of the artifacts have been archived, and since (in my particular case) another jobs uses the artifacts of this job, this build is not usable.

      Therefore any build for which archiving fails should be marked 'unstable', and perhaps even 'failure'.

          [JENKINS-12759] Archiving failure should make build fail (or unstable)

          I again had something similar, now with 1.480.1. This time it looks even worse.

          Background: We're doing a build on a slave, which creates big (4 times 700MB) artifacts, and the master archives them to a Windows share. (Note that I introduced both aspects at the same times: until recently these builds were done on the master, and archived on the master's C:-drive. Yes, I'm using Windows.)

          In this new set-up one of the first builds had its console output end in

            [antcall] Exiting c:\jenkins-slave\workspace\Installer-trunk-core\build.xml.
          
          BUILD SUCCESSFUL
          Total time: 17 minutes 53 seconds
          Archiving artifacts
          

          and then everything seems to break off: there is no Finished: line at the end. I could find not a single related log message, neither on the master or on the slave.

          By comparison, a successful build+archive ends thusly:

            [antcall] Exiting c:\jenkins-slave\workspace\Installer-trunk-core\build.xml.
          
          BUILD SUCCESSFUL
          Total time: 18 minutes 4 seconds
          Archiving artifacts
          Recording fingerprints
          No emails were triggered.
          Installer-trunk-core-ISO is disabled. Triggering skipped
          Collecting metadata...
          Metadata collection done.
          Finished: SUCCESS
          

          I plan to upgrade to 1.509.2 soon. Is there any indication that archiving large files is more reliable currently? Or at least that archiving errors are / can be treated as build failures?

          (And: If anyone is actually reading this, could they respond, so that I don't feel like I'm reporting issues into thin air? Thanks!)

          Marnix Klooster added a comment - I again had something similar, now with 1.480.1. This time it looks even worse. Background: We're doing a build on a slave, which creates big (4 times 700MB) artifacts, and the master archives them to a Windows share. (Note that I introduced both aspects at the same times: until recently these builds were done on the master, and archived on the master's C:-drive. Yes, I'm using Windows.) In this new set-up one of the first builds had its console output end in [antcall] Exiting c:\jenkins-slave\workspace\Installer-trunk-core\build.xml. BUILD SUCCESSFUL Total time: 17 minutes 53 seconds Archiving artifacts and then everything seems to break off: there is no Finished: line at the end. I could find not a single related log message, neither on the master or on the slave. By comparison, a successful build+archive ends thusly: [antcall] Exiting c:\jenkins-slave\workspace\Installer-trunk-core\build.xml. BUILD SUCCESSFUL Total time: 18 minutes 4 seconds Archiving artifacts Recording fingerprints No emails were triggered. Installer-trunk-core-ISO is disabled. Triggering skipped Collecting metadata... Metadata collection done. Finished: SUCCESS I plan to upgrade to 1.509.2 soon. Is there any indication that archiving large files is more reliable currently? Or at least that archiving errors are / can be treated as build failures? (And: If anyone is actually reading this, could they respond, so that I don't feel like I'm reporting issues into thin air? Thanks!)

          For completeness I'm also attaching the original error we got way back when we used 1.409.1: jenkins-1.409.1-archive-artifact-error.txt.

          Marnix Klooster added a comment - For completeness I'm also attaching the original error we got way back when we used 1.409.1: jenkins-1.409.1-archive-artifact-error.txt .

          Daniel Beck added a comment -

          Seems to duplicate JENKINS-2058 unless reproduced in recent Jenkins versions (1.530 or newer or so).

          Daniel Beck added a comment - Seems to duplicate JENKINS-2058 unless reproduced in recent Jenkins versions (1.530 or newer or so).

            Unassigned Unassigned
            marnix_klooster Marnix Klooster
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: