|
||||||||
|
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.
A potential extra angle to this that i have used before (in TeamCity) is to do binary chopping of the changes for builds that take very long.
So take the case of a build taking 1 hours and 20 changes go in.
The overnight build fail with the last change.
I then scripted code to go back 20/2=10 changes back and do a build.
If that passed then go back 10/2=5 builds etc until i found the actual problem.