[
https://issues.jenkins-ci.org/browse/JENKINS-10502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=163040#comment-163040
]
Tuukka Mustonen commented on JENKINS-10502:
-------------------------------------------
Same problem here. I set the {{hudson.tasks.ArtifactArchiver.warnOnEmpty}} to
/etc/default/jenkins (came with jenkins debian-package) and seems to work.
Still, "optional" checkbox in job configuration would be nice.
> Add an option to make archiving the artifacts non-fatal if they don't exist
> ---------------------------------------------------------------------------
>
> Key: JENKINS-10502
> URL: https://issues.jenkins-ci.org/browse/JENKINS-10502
> Project: Jenkins
> Issue Type: Improvement
> Components: core
> Environment: Jenkins 1.421
> Reporter: Thomas Fields
>
> If you tick the box to enable "Archive the artifacts", populate the "Files to
> archive", and your build fails to output those artifacts it will fail with
> something like this:
> {code}
> 12:11:51 Archiving artifacts
> 12:11:51 ERROR: No artifacts found that match the file pattern
> "tfields/Live/Engine/Tools/Layout.*". Configuration error?
> 12:11:57 ERROR: 'tfields/Live/Engine/Tools/Layout.*' doesn't match anything:
> 'tfields' exists but not 'tfields/Live/Engine/Tools/Layout.*'
> 12:11:57 Build step 'Archive the artifacts' changed build result to FAILURE
> {code}
> Depending on what your build actually does, those artifacts might not always
> be created. I'd like to propose that you add an option to make the archiving
> of artifacts non fatal.
> Thanks,
> Tom.
--
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
