1REPORTER-BUGZILLA(1) LIBREPORT MANUAL REPORTER-BUGZILLA(1)
2
6 reporter-bugzilla - Reports problem to Bugzilla.
7
9 reporter-bugzilla [-vbf] [-g GROUP]... [-c CONFFILE]... [-F FMTFILE]
10 [-A FMTFILE2] -d DIR
11 Or:
13 reporter-bugzilla [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE...
15 Or:
17 reporter-bugzilla [-v] [-c CONFFILE]... [-d DIR] -t[ID] -w
19 Or:
21 reporter-bugzilla [-v] [-c CONFFILE]... -h DUPHASH
23
25 The tool reads problem directory DIR. Then it logs in to Bugzilla and
26 tries to find a bug with the same abrt_hash:HEXSTRING in Whiteboard.
27 If such bug is not found, then a new bug is created. Elements of DIR
29 are stored in the bug as part of bug description or as attachments,
30 depending on their type and size.
31 Otherwise, if such bug is found and it is marked as CLOSED DUPLICATE,
33 the tool follows the chain of duplicates until it finds a non-DUPLICATE
34 bug. The tool adds a new comment to found bug.
35 The URL to new or modified bug is printed to stdout and recorded in
37 reported_to element in DIR.
38 Option -t uploads FILEs to the already created bug on Bugzilla site.
40 The bug ID is retrieved from directory specified by -d DIR. If problem
41 data in DIR was never reported to Bugzilla, upload will fail.
42 Option -tID uploads FILEs to the bug with specified ID on Bugzilla
44 site. -d DIR is ignored.
45 Option -w adds bugzilla user to bug’s CC list.
47 Option -r sets the last url from reporter_to element which is prefixed
49 with TRACKER_NAME to URL field. This option is applied only when a new
50 bug is to be filed. The default value is ABRT Server"
51 Configuration file
53 If not specified, CONFFILE defaults to
54 /etc/libreport/plugins/bugzilla.conf. Configuration file lines should
55 have PARAM = VALUE format. The parameters are:
56 Login
58 Login to Bugzilla account.
59 Password
61 Password to Bugzilla account.
62 BugzillaURL
64 Bugzilla HTTP(S) address. (default: https://bugzilla.redhat.com)
65 SSLVerify
67 Use yes/true/on/1 to verify server’s SSL certificate. (default:
68 yes)
69 Product
71 Product bug field value. Useful if you needed different product
72 than specified in /etc/os-release
73 ProductVersion
75 Version bug field value. Useful if you needed different product
76 version than specified in /etc/os-release
77 Parameters can be overridden via $Bugzilla_PARAM environment variables.
79 Formatting configuration files
81 Lines starting with # are ignored.
82 Lines can be continued on the next line using trailing backslash.
84 Format:
86 "%summary
88 summary format"
89 "section
91 element1[,element2]..." The literal text line to be added to
92 Bugzilla comment. Can be empty. (Empty lines are NOT ignored!)
93 Summary format is a line of text, where %element% is replaced by
95 text element's content, and [[...%element%...]] block is used only if
96 %element% exists. [[...]] blocks can nest.
97 Sections can be:
99 - %summary: bug summary format string.
100 - %attach: a list of elements to attach.
101 - text, double colon (::) and the list of comma-separated elements.
102 Elements can be:
104 - problem directory element names, which get formatted as
105 <element_name>: <contents>
106 or
107 <element_name>:
108 :<contents>
109 :<contents>
110 :<contents>
111 - problem directory element names prefixed by "%bare_",
112 which is formatted as-is, without "<element_name>:" and colons
113 - %oneline, %multiline, %text wildcards, which select all corresponding
114 elements for output or attachment
115 - %binary wildcard, valid only for %attach section, instructs to attach
116 binary elements
117 - problem directory element names prefixed by "-",
118 which excludes given element from all wildcards
119 Nonexistent elements are silently ignored.
121 If none of elements exists, the section will not be created.
122 Integration with ABRT events
124 reporter-bugzilla can be used as an ABRT reporter. Example fragment for
125 /etc/libreport/report_event.conf:
126 # Report Python crashes
128 EVENT=report_Bugzilla analyzer=Python
129 reporter-bugzilla -d . -c /etc/libreport/plugins/bugzilla.conf
130
132 -d DIR
133 Path to problem directory.
134 -c CONFFILE
136 Path to configuration file.
137 -b
139 When creating bug, attach binary files too.
140 -f
142 Force reporting even if this problem is already reported.
143 -F CONF_FORMAT_FILE
145 Formatting file for initial comment. Default:
146 /etc/libreport/plugins/bugzilla_format.conf
147 -A CONF_FORMAT_FILE
149 Formatting file for duplicates. Default:
150 /etc/libreport/plugins/bugzilla_format.conf
151 -t[ID]
153 Upload FILEs to the already created bug on Bugzilla site.
154 -w
156 Add bugzilla user to CC list [of bug with this ID]. Applicable only
157 with -t.
158 -h, --duphash DUPHASH
160 Search in Bugzilla by abrt’s DUPHASH and print BUG_ID.
161 -g, --group GROUP
163 When creating a new ticket restrict access to this group only.
164
166 Environment variables take precedence over values provided in the
167 configuration file.
168 Bugzilla_Login
170 Login to Bugzilla account.
171 Bugzilla_Password
173 Password to Bugzilla account.
174 Bugzilla_BugzillaURL
176 Bugzilla HTTP(S) address. (default: https://bugzilla.redhat.com)
177 Bugzilla_SSLVerify
179 Use yes/true/on/1 to verify server’s SSL certificate. (default:
180 yes)
181 Bugzilla_Product
183 Product bug field value. Useful if you needed different product
184 than specified in /etc/os-release
185 Bugzilla_ProductVersion
187 Version bug field value. Useful if you needed different product
188 version than specified in /etc/os-release
189 http_proxy
191 the proxy server to use for HTTP
192 HTTPS_PROXY
194 the proxy server to use for HTTPS
195
197 /usr/share/libreport/conf.d/plugins/bugzilla.conf
198 Readonly default configuration files.
199 /etc/libreport/plugins/bugzilla.conf
201 Configuration file.
202 /etc/libreport/plugins/bugzilla_format.conf
204 Configure formating for reporting.
205
207 report_event.conf(5), bugzilla_format.conf(5)
208
210 · ABRT team
211LIBREPORT 2.1.11.1 11/13/2018 REPORTER-BUGZILLA(1)