Versions before 3.6 don't have SEE ALSO sections, so we have to list out all the documentation explicitly: command is one of: login - log into the given. Note also that the JSON-RPC WebService was added in 3.6, so versions before 3.6 do not have JSON-RPC support. bugzilla is a command-line utility that allows access to the XML-RPC interface provided by Bugzilla. In each of these pages, see the "SEE ALSO" section for links to the documentation of each function that the WebService provides. If you want to read the documentation for stable versions of Bugzilla directly, here they are. It also has a sub-section called "WebService Methods", which links to the documentation for all of the actual functions you can call in the Bugzilla WebService.
The "SEE ALSO" section has "Server Types", which describes specifics about how to use the WebService on XML-RPC vs JSON-RPC. (You will see the "History" section at the end of every method's individual documentation.) Make sure to read the "History" section of the docs for every method that you use, though, so that you understand how it changed across versions of Bugzilla and when it was added. But I have no idea how to debug and see what is missing I did an installation. In many cases, you can just read this very latest documentation for the WebService, because it accurately describes the version in which every feature was added. The XML-RPC Interface feature is not available in this Bugzilla It seems that the XML-RPC interface is not detected. Note that it is a completely separate application from Bugzilla it uses existing methods (XML-RPC, CSV representations, and raw HTML) to access Bugzilla data, which it transforms into JSON and serves RESTfully over HTTP. Note that in a future version, probably 6.0, XML-RPC and JSON-RPC will be considered deprecated in order to focus future development on the REST interface.īzAPI is a separate service interfacing with Bugzilla and providing a REST interface, different from 5.0's native REST. If(!int.The currently released versions of Bugzilla support XML-RPC, JSON-RPC and starting with version 5.0 RESTful interface. [XmlRpcUrl(" public interface IBugZillaInterface : IXmlRpcProxy XmlRpcStruct bugs = (XmlRpcStruct)returnValue These values are accessed like how you would access a Dictionary value in C#. For more details on these, reference the Bugzilla documentation, here.
Each bug will generally contain the following fields (in no particular order). The XmlRpcStruct return value will generally have two keys, “bugs” and “faults”. If everything was done correctly, this will populate the “returnValue” with the information for the bugs you provided in the format of an XmlRpcStruct (an XmlRpcStruct is basically an array of key/value pairs like a Dictionary). IBugzillaInterface bugzilla = XmlRpcProxyGen.Create() īugzilla.NonStandard = XmlRpcNonStandard.AllowStringFaultCode Once we have the Interface defined, it’s easy to use it… This keeps us from having to mess with the Login interfaces, and keeps it simple for this implementation. In the later specs, you can pass a Bugzilla_login and Bugzilla_password variable to any interface and it will login as that user.
To the get method we are passing in a login, password and the IDs of the bugs we wish to be returned. In this code, we are defining the interface and providing the URL to our Bugzilla installation (XmlRpcUrl) and then defining the “get” method. XmlRpcStruct Get(string Bugzilla_login, string Bugzilla_password, int ids) [XmlRpcUrl(" public interface IBugzillaInterface : IXmlRpcProxy Here is the basic and super simple interface for getting a bug out of Bugzilla using the “Bug.get” interface. The way the xmlrpcnet packages work is by setting up and interface that then is turned into a proxy for the XML-RPC service. You can get more information on the XML-RPC spec for Bugzilla, here.įor the actual Bug.get call, the documentation is, here. Once the XMLRPCNET packages are installed, you should be able to see the References added to your project.