|
||||||||
|
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 API calls resulting in these exceptions do not actually produce JSON/XML output, so that's not a real solution for you.
Since you're writing that it's been "working fine until now" I have to ask: what changed? Jenkins update? If so, from which version to 1.577? Plugins installed? Updated? If so, which?
"It's not just this plugin. It's all of them" seems like an exaggeration – could you provide the list of plugins (or classes/fields from the first line of the exception message) affected here?
A possible workaround restoring functionality would be in looking to filter API output, e.g. the XML API has an argument "tree" that allows you to only retrieve a subset of fields.