blob: 6002ccf210274cb1a86aa54e0a26311509c55ca8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
|
abrt-action-buzilla(1)
====================
NAME
----
abrt-action-bugzilla - Reports problem to Bugzilla.
SYNOPSIS
--------
'abrt-action-bugzilla' [-v] [-c CONFFILE] -d DIR
DESCRIPTION
-----------
The tool reads problem dump 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.redht.com)
'SSLVerify'::
Use yes/true/on/1 to verify Bugzilla ssl certificate. (default: yes)
Parameters can be overridden via $Bugzilla_PARAM environment variables.
Integration with ABRT events
~~~~~~~~~~~~~~~~~~~~~~~~~~~~
'abrt-action-bugzilla' can be used as an ABRT reporter. Example
fragment for /etc/abrt/abrt_events.conf:
------------
# Report Python crashes
EVENT=report_Bugzilla analyzer=Python
abrt-action-bugzilla -d . -c /etc/abrt/plugins/Bugzilla.conf
------------
OPTIONS
-------
-d DIR::
Path to dump directory.
-c CONFFILE::
Path to configration file.
SEE ALSO
--------
abrt_event.conf
|
