|
||||||||
|
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 |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Daniel,
Thanks for the pointer, I have installed the VersionColumn Plugin, and its not complaining for any of the slave jars, so I believe that's not the issue. Moreover, when I am trying a release build, I am executing it on master server only where Jenkins is installed and not using any slave.
When I did further analysis between various build jobs I have, found a pattern that its causing this exception only for the job which is having a heavy maven build in terms of modules, which takes almost an hour for us to get all the modules built, may be it has some relation with timing or some threading issue in the core part of code which is leading to this error. Just wanted to share my analysis, might give you some clue to diagnose the problem. Thanks!
Regards,
Swapnil