|
||||||||
|
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.
Okay, I think I've narrowed it down to this API call:
/job/scm-poll-drive-HEAD//300/api/xml?depth=4&wrapper=fingerprints&xpath=//fingerprint[../result/text()=%27SUCCESS%27%20and%20starts-with(fileName/text(),%27scm-poll-drive-HEAD-%27)%20and%20contains(fileName/text(),%27.tar.bz2%27)]/usage/name[starts-with(text(),%27drive-%27)]
Which translates to:
/job/scm-poll-drive-HEAD//300/api/xml?depth=4&wrapper=fingerprints&xpath=//fingerprint[../result/text()='SUCCESS' and starts-with(fileName/text(),'scm-poll-drive-HEAD-') and contains(fileName/text(),'.tar.bz2')]/usage/name[starts-with(text(),'drive-')]
What I am trying to do here is get the name of fingerprints that end with '.tar.bz2', that have been used by downstream builds with names beginning 'drive-'. This is to do with our pipeline and how we create change lists. The plugins that provide change lists, don't work in the way we need them to, so we generate our own.
The thing that causes all the exceptions appears to be the depth=4 parameter.
Do we really care that much about plugins that have no @ExportedBean to dump the entire stack trace at INFO level? Can't we treat exceptions for @ExportedBean as DEBUG level errors?