|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [JIRA] (JENKINS-13920) Provide an option whether... [email protected] (JIRA)
- [JIRA] (JENKINS-13920) Provide an option wh... [email protected] (JIRA)
- [JIRA] (JENKINS-13920) Provide an option wh... [email protected] (JIRA)
- [JIRA] (JENKINS-13920) Provide an option wh... [email protected] (JIRA)
- [JIRA] (JENKINS-13920) Provide an option wh... [email protected] (JIRA)
- [JIRA] (JENKINS-13920) Provide an option wh... [email protected] (JIRA)
- [JIRA] (JENKINS-13920) Provide an option wh... [email protected] (JIRA)
- [JIRA] (JENKINS-13920) Provide an option wh... [email protected] (JIRA)

Try to actually reproduce the issue as described, instead of something that looks vaguely similar. If the disk fills up, or the connection aborts for some reason, and you cannot archive the build output completely, the build should fail. There's no output, after all. Not everyone has the luxury of using an artifact repository, or of having only artifacts of a few MB, so archiving using Jenkins is vital for some users. The issues you link to are still unfixed and your "example" is completely unrelated.