|
||||||||
|
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.
If you would like to reduce the severity e.g. to "Major" please feel free to do so.
But I disagree on it being only an "inconvenience" which is not worth to be addressed.
For us it makes Jenkins almost unusable for large scale deployments.
Either our Jenkins master dies at some point because it runs out of storage or we have to accept "loss of data" in terms of removing build logs way earlier than it should be necessary.
Arguably Jenkins would benefit from a global object to not print upstream triggers at all.
The same as SVN might benefit from an option to be less verbose about what it checked out.
But the current listing of highly redundant upstream triggers is simply wrong.
It (the redundant part) does not contain any information at all!
The especially disappointing part is that it was fixed before and nobody seems to care about the regression for now a year.
I fear that this will not change with the severity lowered and the ticket will remain unresolved forever.