|
||||||||
|
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/groups/opt_out.
Fixing by limiting how many transitive upstream causes are recorded to begin with.
Note that this will not help with existing build records, only for new builds. But as in
JENKINS-14814you can run some simple scripts to erase upstream cause information from old build records, if you need to keep those builds for whatever reason.I made a couple of other commits (6023716 and 9e58d94) with some related cosmetic fixes; the change in 1.482 failed to display transitive causes in a tree so they were nearly impossible to read.