|
||||||||
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) Mon, 05 Nov 2012 06:41:50 -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)
Having the same issue here, but do not have envinject plugin installed at all.
Have found that restarting the affected slave temporarily prevents the error.
Suspect that your "fix" actually works similarly due to the restart when removing the plugin.
My only suspect cause is a minor difference in the JVM versions between master (1.6.0_26) and slave (1.6.0_21)