|
||||||||
|
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.
Maybe this is a viable solution for you for jobs that are affected?
https://github.com/jenkinsci/compress-buildlog-plugin
Have you considered other workarounds at all, like having "Trigger" jobs that only get all the upstream triggers, and then trigger the actual downstream job via an API call? It's not as nice, but it's simple and works. Since you consider trigger information irrelevant, this would simply kill the chain off. (As would using the API technique for the default trigger mechanism, but that may be more inconvenient.) Dump the trigger job's logs earlier.
My guess would be that the Cloudbees folks change something for their customers if it's not actively harmful even for weak/questionable reasons, and that this just doesn't make the relevance threshold otherwise.