[
https://issues.jenkins-ci.org/browse/JENKINS-12759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marnix Klooster updated JENKINS-12759:
--------------------------------------
Description:
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'.
was:
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'.
> Archiving failure should make build fail (or unstable)
> ------------------------------------------------------
>
> Key: JENKINS-12759
> URL: https://issues.jenkins-ci.org/browse/JENKINS-12759
> Project: Jenkins
> Issue Type: Bug
> Components: core
> Affects Versions: current
> Reporter: Marnix Klooster
>
> 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'.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jenkins-ci.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
