[JIRA] [core] (JENKINS-22238) IOException archiving artifacts in 1.550

Mon, 17 Mar 2014 18:43:25 -0700

Conversation from IRC:

(06:38:53 PM) kohsuke: spudly:  If you restart Jenkins does the problem persist?
(06:39:07 PM) kohsuke: I wonder if the extracted war directory is getting wiped away
(06:39:45 PM) spudly: Ah, that's not something I'm able to do right now unfortunately. As far as I know the master hasn't been touched or restarted or anything like that.
(06:40:29 PM) kohsuke: When you get around to do that, please retry a build on this problematic slave and report back if the problem persists
(06:40:56 PM) spudly: Right - I can restart the slave right now, but I suspect you're suggesting restarting the master?
(06:40:56 PM) kohsuke: If my guess is right, it'll be OK for a while, then eventually your temp directory cleaner or something comes in, then it starts to break
(06:41:04 PM) kohsuke: Yes, I'm talking about restarting the master
(06:41:30 PM) spudly: Hmm, Jenkins /tmp/ still exists.
(06:41:37 PM) kohsuke: Sine we switched Winestone to Jetty-based 2.0, I think we haven't been controlling where it explodes the war file very closely
(06:41:46 PM) kohsuke: I should check
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

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to