|
||||||||
|
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 [email protected].
For more options, visit https://groups.google.com/d/optout.
Over in JENKINS-15156 I mentioned I wrote a tool in ruby for analyzing and fixed build history problems: https://github.com/docwhat/jenkins-job-checker
If you run jobber.rb with --solve it'll try to fix problems, otherwise it just prints out how it would have solved the problem (in addition of a description of the problem(s)).
You have to restart Jenkins (or better yet, run it while Jenkins is down) afterwards. A "reload from disk" may also work instead as well.