|
||||||||
|
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.
Thank you for pointing out potential workarounds.
The compression might be an option but also add additional load on the master. I don't know if that would be acceptable without further testing. (Update: after taking a brief look at the repository / plugin page I don't think this is mature enough to be used in production.)
Replacing the project dependencies with a custom trigger mechanism wouldn't be difficult (since we generate the jobs anyway) but I don't want to remove that valuable information.
This seems to be working around core Jenkins elements.
Also the trigger reason in the log is nice - if it would not contain the exponentially exploded redundant information.