Yes, we have API servers that you can allow through your firewalls for Pivotal Tracker integration with your Bugzilla server. Hope it helps.įinally, we get asked if you can integrate Tracker with Bugzilla if it’s behind your firewall. The above should cover the most common problems. We can provide steps to help you with this if you need them. In that case, determining if your bugs have any multi-byte characters and removing them, should resolve the problem. These characters cause the length of the data stream that the web server sends to us to be incorrect, and we are unable to parse the XML on our side. This is usually a result of pasting text into a bug from rich text email or office documents.
Bugzilla xml rpc Patch#
It’s been fixed in the patch referenced in the bug, but by the time you read this, there may be more recent updates. Only text/xml and application/xml are allowed.”) could be the result of the following Bugzilla bug: However, if you are using version 4.0.5, a bad response (such as “Application failed during request deserialization: 32612: When using XML-RPC, you cannot send data as text/xml charset=utf-8. For example, if contains, “The XML-RPC Interface feature is not available in this Bugzilla.” it means you need to enable the XMLRPC interface on your Bugzilla server. In general the response’s content should help you troubleshoot. If this is not the kind of response you get, then your server is still not setup correctly. If the response printed by the curl command accessing your Bugzilla server is like this, then the Tracker integration should be able to access your Bugzilla server. If all is well, the response should look like this: For example:Ĭurl -X POST -H"Content-Type: text/xml" -d
To see a successful version request, run the command against the Bugzilla “Landfill” test server. Create a file called version.xml with the following text:Ĭurl -X POST -H"Content-Type: text/xml" -d /xmlrpc.cgi To run this you’ll need access to a machine that has the CURL command.
Bugzilla xml rpc install#
Check to see if these modules are there and if not, install them.Once that’s done, you can test it using the following. It will tell you what modules are installed, and what optional modules can be installed (and what they will enable). To determine if you have them installed (or to get the commands necessary to install them), go to the directory where you installed Bugzilla on your server and run the script. You may need to install one or more optional Perl modules, i.e.To check, log in to your Bugzilla instance and use the advanced search options to find a small number of bugs, to help you change the default values to exclude all but those, and see if they’ll be pulled in. If you haven’t changed the integration’s “Bug ‘Status’ values to exclude” (currently RESOLVED, VERIFIED, CLOSED), these defaults could be trying to pull in too much data and hence failing.That said, at the time of writing, we recommend 4.0.9 as we’re looking into an issue with the the 4.2.0 release and possibly some preceding minor versions and release candidates. We only support versions 3.4.x and above.You can take the first error literally, but there are also some other causes for it which aren’t obvious. “Unable to load bugs – There was a problem processing your request.” “Unable to load bugs – Please check your URL and remember to include and exclude the xmlrpc.cgi.” The following also applies to other error messages, but these are the most common: In general all you need is here: īut if you do receive an error message instead of bugs loading in your Bugzilla integration panel, here are some tips to get past them. Bugzilla is a popular Tracker integration and fairly straightforward to set up.
0 kommentar(er)
