![]() If you don't own this saved search, you must passed -savedsearch_sharer_id. Search using bugzilla's quicksearch functionality. Specify individual bugs by IDs, separated with commasĮmail: search reporter email for given address See the -from-url option for a way to use powerful Web UI queries from the command line. Note: querying via explicit command line options will only get you so far. ‘query’ specific optionsĬertain options can accept a comma separated list to query multiple values, including -status, -component, -product, -version, -id. You can use RPM-style tags that match bug fields, e.g.: '%, etc. One line summary of the bug (useful for scripts) Output additional bug information (keywords, Whiteboards, etc.) These options are shared by several commands, for tweaking the text output of the command results. For example if your bugzilla instance has a custom field cf_my_field, do: -field cf_my_field=VALUE FIELD is the raw name used by the bugzilla instance. Manually specify a bugzilla XMLRPC field. For example, to set a flag named devel_ack, do -flag devel_ack+ Unset a flag with the 'X' value, like -flag needinfoX Not every option works for each command though. These options are shared by some combination of the 'new', 'query', and 'modify' sub commands. Token file to use for bugzilla authentication Consider using this if you are depending on cached credentials, to ensure that when they expire the tool errors, rather than subtly change output.ĭon't save any bugzilla cookies or tokens to disk, and don't use any pre-existing credentials.Ĭookie file to use for bugzilla authentication Raise an error if we aren't logged in to bugzilla. The session (login token) will be restricted to the current IP address. Run interactive "login" before performing the specified command. * info - get info about the given bugzilla instance GLOBAL OPTIONSĭon't error on invalid bugzilla SSL certificateĬlient side certificate file needed by the webserver. * attach - attach files to existing bugs, or get attachments * query - search for bugs matching given criteria * login - log into the given bugzilla instance To read the man page for bugzilla in Linux: ~]$ man 1 bugzilla NAMEīugzilla - command-line interface to Bugzilla over XML-RPC SYNOPSISīugzilla DESCRIPTIONīugzilla is a command-line utility that allows access to the XML-RPC interface provided by Bugzilla. Errors with a numeric code higher than 100000 are errors thrown by the JSON-RPC library that Bugzilla uses, not by Bugzilla.Linux Home > Manual Sections > 1 > bugzilla bugzilla(1) - Linux Man Page Here's a call to User.get, with several parameters: jsonrpc.cgi?method=User.get¶ms=[ ,Įvery error has a "code", as described in "ERRORS" in Bugzilla::WebService. The simplest example is a call to Bugzilla.time: jsonrpc.cgi?method=Bugzilla.time With the params item being a JSON string. Simply send the values that you'd normally send for each JSON-RPC argument as URL parameters, You have to use the Bugzilla_login and Bugzilla_password method described at "LOGGING IN" in Bugzilla::WebService. ![]() Only methods that simply return data can be used over GET. Methods that modify the database or cause some action to happen in Bugzilla cannot be called over GET. You can also access certain methods by using GET (a normal webpage load). ![]() The most powerful way to access the JSON-RPC interface is by HTTP POST. Then your JSON-RPC client would access the API via: Connecting via GET The endpoint for the JSON-RPC interface is the jsonrpc.cgi script in your Bugzilla installation. We recommend that you use JSON-RPC 1.0 instead of 1.1, JSON-RPCīugzilla supports both JSON-RPC 1.0 and 1.1. Please use the Bugzilla::WebService::Server::XMLRPC|XML-RPC interface. Please note that everything about this JSON-RPC interface is EXPERIMENTAL. This documentation describes things about the Bugzilla WebService that are specific to JSON-RPC.įor a general overview of the Bugzilla WebServices, Bugzilla::WebService::Server::JSONRPC - The JSON-RPC Interface to Bugzilla DESCRIPTION
0 Comments
Leave a Reply. |