|
||||||||
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... 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 should clarify, in case it is relevant – I normally dont restart all of the slaves every time I restart the master. In this case all the slaves were already running their listener processes. In this repro process, I restarted only the master.
I can consistently repro this issue every time I restart the master.
Still happening with Jenkins 1.492