|
||||||||
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.
The problem is that the repeated logging of all upstream causes can result in extremely large build logs.
As mentioned in the referenced original ticket that can be even up to 100 MB for a single job.
Having numerous jobs / builds with such extensive logs will basically make Jenkins completely unable to operate.
The bug has been fixed before but has reappeared since then.
I recent example has "only" 1.5 MB: http://jenkins.ros.org/job/ros-hydro-metapackages_binarydeb_precise_amd64/1102/consoleFull
Just pick a random upstream build which triggered this jobs and see how many repetitions are in the log.