[JIRA] [core] (JENKINS-21605) Logging all UpstreamCause's floods Jenkins in large setups

[jgl...@cloudbees.com (JIRA)]

Jesse Glick commented on JENKINS-21605 Logging all UpstreamCause's floods Jenkins in large setups it should show ALL direct upstream projects which triggered the build Probably yes. in combination with that the current threshold for the recursion depth (of 11) is already resulting in too big output Right, that is the bug here. what kind of threshold are you proposing No exact proposal, but perhaps something like: always display all direct upstream causes, and then use DeeplyNestedUpstreamCause for indirect causes when either a certain depth is exceeded, or the total number of non-direct causes exceeds some threshold. In fact this is exactly what JENKINS-15747 is supposed to do (it was JENKINS-14814 which fixed only the depth). There is a test demonstrating that it works at least in some circumstances. Perhaps you are hitting some other corner case. Add a test for it and the fix should follow.

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.