|
||||||||
|
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.
I have updated the Groovy script to generate a job topology like this:
01 depends on root
02 depends on 01
...
40 depends on 39
leaf depends on: 01-40
The result can be found here: http://54.183.26.131:8080/view/jenkins21605/job/jenkins21605_leaf/lastSuccessfulBuild/
The build log is already 84 KB in size (just for logging the upstream causes).
I think the "best" approach to address this is not to add another threshold but simply give the user the option not to log the recursive upstream cause.
It is perfectly fine to list all "Started by upstream project" lines for all the upstream dependencies.
But optionally not outputting the ever increasing "originally caused by" would reduce the output to linear size (linear to the number of upstream dependencies).
And the user can still navigate the hierarchy of upstream causes by following the upstream build links.
Do you agree that this test is sufficient?
Do you agree that the proposed option would be a reasonable approach to address the problem or do you see a better approach?