1REPORTER-MANTISBT(1) LIBREPORT MANUAL REPORTER-MANTISBT(1)
2
6 reporter-mantisbt - Reports problem to Mantis Bug Tracker.
7
9 reporter-mantisbt [-vrf] [-c CONFFILE]... [-F FMTFILE] [-A FMTFILE2] -d
10 DIR
11 Or:
13 reporter-mantisbt [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE...
15 Or:
17 reporter-mantisbt [-v] [-c CONFFILE]... -h DUPHASH
19
21 The tool reads problem directory DIR. Then it logs in to MantisBT and
22 tries to find an issue with the same duphash HEXSTRING in abrt_hash
23 field.
24 If such issue is not found, then a new issue is created. Elements of
26 DIR are stored in the issue as part of issue description or as
27 attachments, depending on their type and size.
28 Otherwise, if such issue is found and it is marked as CLOSED DUPLICATE,
30 the tool follows the chain of duplicates until it finds a non-DUPLICATE
31 issue. The tool adds a new note to found issue.
32 The URL to new or modified issue is printed to stdout and recorded in
34 reported_to element in DIR.
35 Option -t uploads FILEs to the already created issue on MantisBT site.
37 The issue ID is retrieved from directory specified by -d DIR. If
38 problem data in DIR was never reported to MantisBT, upload will fail.
39 Option -tID uploads FILEs to the issue with specified ID on MantisBT
41 site. -d DIR is ignored.
42 Option -r sets the last url from reporter_to element which is prefixed
44 with TRACKER_NAME to URL field. This option is applied only when a new
45 issue is to be filed. The default value is ABRT Server"
46 Configuration file
48 If not specified, CONFFILE defaults to
49 /etc/libreport/plugins/mantisbt.conf. Configuration file lines should
50 have PARAM = VALUE format. The parameters are:
51 Login
53 Login to MantisBT account.
54 Password
56 Password to MantisBT account.
57 MantisbtURL
59 MantisBT HTTP(S) address. (default: http://localhost/mantisbt)
60 SSLVerify
62 Use yes/true/on/1 to verify server’s SSL certificate. (default: no)
63 Project
65 Project issue field value. Useful if you needed different project
66 than specified in /etc/os-release
67 ProjectVersion
69 Version issue field value. Useful if you needed different project
70 version than specified in /etc/os-release
71 CreatePrivate
73 Create private MantisBT issue. (default: no)
74 Parameters can be overridden via $Mantisbt_PARAM environment variables.
76 Formatting configuration files
78 Lines starting with # are ignored.
79 Lines can be continued on the next line using trailing backslash.
81 Format:
83 "%summary
85 summary format"
86 "section
88 element1[,element2]..." The literal text line to be added to
89 MantisBT Description or Additional information. Can be empty.
90 (Empty lines are NOT ignored!)
91 Summary format is a line of text, where %element% is replaced by
93 text element's content, and [[...%element%...]] block is used only if
94 %element% exists. [[...]] blocks can nest.
95 Sections can be:
97 - %summary: issue Summary format string.
98 - %attach: a list of elements to attach.
99 - %Additional info: issue Additional Information content.
100 - text, double colon (::) and the list of comma-separated elements.
101 Description and Additional information MantisBT's fields:
103 All text, double colons (::) and lists of comma-separated elements which
104 are placed above the section '%Additional info::' in the configuration file are
105 stored in the 'Description' field in MantisBT. All text etc. which are placed
106 under the '%Additional info::' are stored in the 'Additional information' field.
107 For example:
109 |:: comment | (Description)
110 | | (Description)
111 |Package:: package | (Description)
112 | | (Description)
113 |%Additional_info:: |
114 |%reporter% | (Additional info)
115 |User:: user_name,uid | (Additional info)
116 | | (Additional info)
117 |Directories:: root,cwd | (Additional info)
118 Elements can be:
120 - problem directory element names, which get formatted as
121 <element_name>: <contents>
122 or
123 <element_name>:
124 :<contents>
125 :<contents>
126 :<contents>
127 - problem directory element names prefixed by "%bare_",
128 which is formatted as-is, without "<element_name>:" and colons
129 - %oneline, %multiline, %text wildcards, which select all corresponding
130 elements for output or attachment
131 - %binary wildcard, valid only for %attach section, instructs to attach
132 binary elements
133 - problem directory element names prefixed by "-",
134 which excludes given element from all wildcards
135 Nonexistent elements are silently ignored.
137 If none of elements exists, the section will not be created.
138 Integration with ABRT events
140 reporter-mantisbt can be used as an ABRT reporter. Example fragment for
141 /etc/libreport/report_event.conf:
142 # Report Python crashes
144 EVENT=report_CentOSBugTracker analyzer=Python
145 reporter-mantisbt -d . -c /etc/libreport/plugins/mantisbt.conf
146
148 -d DIR
149 Path to problem directory.
150 -c CONFFILE
152 Path to configuration file.
153 -f
155 Force reporting even if this problem is already reported.
156 -F CONF_FORMAT_FILE
158 Formatting file for new issues. Default:
159 /etc/libreport/plugins/mantisbt_format.conf
160 -A CONF_FORMAT_FILE
162 Formatting file for duplicates. Default:
163 /etc/libreport/plugins/mantisbt_formatdup.conf
164 -t[ID]
166 Upload FILEs to the already created issue on MantisBT site.
167 -h, --duphash DUPHASH
169 Search in MantisBT by abrt’s DUPHASH and print ISSUE_ID.
170 -r TRACKER_NAME
172 Set the last url from reporter_to element which is prefixed with
173 TRACKER_NAME to URL field in MantisBT.
174
176 Environment variables take precedence over values provided in the
177 configuration file.
178 Mantisbt_Login
180 Login to MantisBT account.
181 Mantisbt_Password
183 Password to MantisBT account.
184 Mantisbt_MantisbtURL
186 MantisBT HTTP(S) address. (default: http://localhost/mantisbt)
187 Mantisbt_SSLVerify
189 Use yes/true/on/1 to verify server’s SSL certificate. (default: no)
190 Mantisbt_Project
192 Project issue field value. Useful if you needed different project
193 than specified in /etc/os-release
194 Mantisbt_ProjectVersion
196 Version issue field value. Useful if you needed different project
197 version than specified in /etc/os-release
198 Mantisbt_CreatePrivate
200 Create private MantisBT issue. (default: no)
201
203 /usr/share/libreport/conf.d/plugins/mantisbt.conf
204 Readonly default configuration files.
205 /etc/libreport/plugins/mantisbt.conf
207 Configuration file.
208 /etc/libreport/plugins/mantisbt_format.conf
210 Configure formating for reporting.
211 /etc/libreport/plugins/mantisbt_formatdup.conf
213 Configure formating for reporting duplicates.
214
216 report_event.conf(5), mantisbt_format.conf(5),
217 mantisbt_formatdup.conf(5)
218
220 · ABRT team
221LIBREPORT 2.1.11.1 11/13/2018 REPORTER-MANTISBT(1)