|
||||||||
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-15552) envinject plugin v1.72 might be incompatible with Jenkins v.1486
greg.al...@nomura.com (JIRA) Wed, 05 Dec 2012 02:12:48 -0800
- [JIRA] (JENKINS-15552) envinject plugin... greg.al...@nomura.com (JIRA)
- [JIRA] (JENKINS-15552) envinject p... greg.al...@nomura.com (JIRA)
- [JIRA] (JENKINS-15552) envinject p... gregory.boissi...@gmail.com (JIRA)
- [JIRA] (JENKINS-15552) envinject p... sdrot...@gmail.com (JIRA)
- [JIRA] (JENKINS-15552) envinject p... greg.al...@nomura.com (JIRA)
- [JIRA] (JENKINS-15552) envinject p... sdrot...@gmail.com (JIRA)
- [JIRA] (JENKINS-15552) envinject p... sdrot...@gmail.com (JIRA)
- [JIRA] (JENKINS-15552) envinject p... greg.al...@nomura.com (JIRA)
- [JIRA] (JENKINS-15552) envinject p... gregory.boissi...@gmail.com (JIRA)
I think one possible cause of this issue is if you aggressively clean the TEMP directory on the master or slave servers. It may be that removal of one of the remoting files that hudson/jenkins creates there causes this cryptic exception. Even the plain old Windows disk clean up might cause this.
Perhaps Jenkins could lock these temp files while it runs so that they can't accidentally be deleted?