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

Archiving failure should make build fail (or unstable)

XMLWordPrintable

    • 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'.

        1. jenkins-1.409.1-archive-artifact-error.txt
          7 kB

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

          Marnix Klooster created issue -
          Marnix Klooster made changes -
          Description Original: If archiving fails, i.e., the console log ends as follows (as for example seen in the description of JENKINS-7038):
          {noformat}
          [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
          {noformat}
          then apparently Jenkins (1.424.2) 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'.           		New: If archiving fails, i.e., the console log ends as follows (as for example seen in the description of JENKINS-7038):
          {noformat}
          [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
          {noformat}
          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'.
          Dima Korobskiy made changes -
          Link New: This issue is related to JENKINS-13920 [ JENKINS-13920 ]
          bap made changes -
          Link Original: This issue is related to JENKINS-13920 [ JENKINS-13920 ]
          Marnix Klooster made changes -
          Attachment New: jenkins-1.409.1-archive-artifact-error.txt [ 24143 ]
          Daniel Beck made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Resolved [ 5 ]
          Daniel Beck made changes -
          Link New: This issue duplicates JENKINS-2058 [ JENKINS-2058 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 143216 ] New: JNJira + In-Review [ 190445 ]

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

              Created:
              Updated:
              Resolved: