|
||||||||
|
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-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)
- [JIRA] (JENKINS-15957) All build executor... [email protected] (JIRA)

Another observation: I don't know if this is related to EnvInject at all? That's where our build appears to be hanging up when the problem does reveal itself. I know this much, it's very annoying: I can't be monitoring Jenkins all the time wondering whether my build chain is working. That's the point of automating the chain so I can be hands off.