|
||||||||
|
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-15351) Exception while pro... [email protected] (JIRA)
- [JIRA] (JENKINS-15351) Exception whil... [email protected] (JIRA)
- [JIRA] (JENKINS-15351) Exception whil... [email protected] (JIRA)
- [JIRA] (JENKINS-15351) Exception whil... [email protected] (JIRA)
- [JIRA] (JENKINS-15351) Exception whil... [email protected] (JIRA)
- [JIRA] (JENKINS-15351) Exception whil... [email protected] (JIRA)
- [JIRA] (JENKINS-15351) Exception whil... [email protected] (JIRA)
- [JIRA] (JENKINS-15351) Exception whil... [email protected] (JIRA)
- [JIRA] (JENKINS-15351) Exception whil... [email protected] (JIRA)

We're seing this as well using Jenkins 1.470 and DRY Plugin 2.28.
The stack trace scared a colleague because he though that his release build had failed, when in fact it had succeeded.