REPORTER-BUGZILLA(1) LIBREPORT MANUAL REPORTER-BUGZILLA(1)NAMEreporter-bugzilla - Reports problem to Bugzilla.
SYNOPSISreporter-bugzilla [-vbf] [-c CONFFILE] -d DIR
Or:
reporter-bugzilla [-v] [-c CONFFILE] [-d DIR] -t[ID] FILE...
Or:
reporter-bugzilla-h DUPHASH
DESCRIPTION
The tool reads problem directory DIR. Then it logs in to Bugzilla and
tries to find a bug with the same abrt_hash:HEXSTRING in Whiteboard.
If such bug is not found, then a new bug is created. Elements of DIR
are stored in the bug as part of bug description or as attachments,
depending on their type and size.
Otherwise, if such bug is found and it is marked as CLOSED DUPLICATE,
the tool follows the chain of duplicates until it finds a non-DUPLICATE
bug. The tool adds a new comment to found bug.
The URL to new or modified bug is printed to stdout and recorded in
reported_to element in DIR.
Configuration file
Configuration file lines should have PARAM = VALUE format. The
parameters are:
Login
Login to Bugzilla account.
Password
Password to Bugzilla account.
BugzillaURL
Bugzilla HTTP(S) address. (default: https://bugzilla.redhat.com)
SSLVerify
Use yes/true/on/1 to verify server’s SSL certificate. (default:
yes)
OSRelease
OS release string. Useful if your /etc/system-release is
non-standard.
Parameters can be overridden via $Bugzilla_PARAM environment variables.
Integration with ABRT events
reporter-bugzilla can be used as an ABRT reporter. Example fragment for
/etc/libreport/report_event.conf:
# Report Python crashes
EVENT=report_Bugzilla analyzer=Python
reporter-bugzilla-d . -c /etc/libreport/plugins/bugzilla.conf
OPTIONS-d DIR
Path to problem directory.
-c CONFFILE
Path to configuration file.
-b
When creating bug, attach binary files too.
-f
Force reporting even if this problem is already reported.
-t[ID]
Upload FILEs to the already created bug on Bugzilla site.
-h, --duphash
Search in bugzilla by abrt’s DUPHASH and return BUG-ID
SEE ALSO
abrt_event.conf
AUTHORS
· ABRT team
LIBREPORT 2.0.10 05/21/2012 REPORTER-BUGZILLA(1)
