|
||||||||
|
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.
Interesting theory! Not sure how to prove it directly if I can't hit that page when Jenkins isn't responding. I will try to see if I can load it next time it happens, though.
For fun, I tried recreating the project and then diffed the resulting config.xml between the two. No material differences found. Same if I diff the multibranch config.xml for the individual branches.
Is it possible there could be old build records/artifacts that could be at fault? Would OldDataMonitor possibly trigger if there was somehow bad build history? I'm going to need to let it rebuild all of the branches which is going to take some time.