NAME
reporter-mantisbt - Reports problem to Mantis Bug Tracker. SYNOPSIS
reporter-mantisbt [-vrf] [-c CONFFILE]... [-F FMTFILE] [-A FMTFILE2] -d DIR Or:
reporter-mantisbt [-v] [-c CONFFILE]... [-d DIR] -t[ID] FILE... Or:
reporter-mantisbt [-v] [-c CONFFILE]... -h DUPHASH DESCRIPTION The tool reads problem directory DIR. Then it logs in to MantisBT and tries to find an issue with the same duphash HEXSTRING in abrthash field. If such issue is not found, then a new issue is created. Elements of DIR are stored in the issue as part of issue description or as attachments, depending on their type and size. Otherwise, if such issue is found and it is marked as CLOSED DUPLICATE,
the tool follows the chain of duplicates until it finds a non-DUPLICATE issue. The tool adds a new note to found issue. The URL to new or modified issue is printed to stdout and recorded in reportedto element in DIR.
Option -t uploads FILEs to the already created issue on MantisBT site.
The issue ID is retrieved from directory specified by -d DIR. If problem data in DIR was never reported to MantisBT, upload will fail.
Option -tID uploads FILEs to the issue with specified ID on MantisBT
site. -d DIR is ignored.
Option -r sets the last url from reporterto element which is prefixed with TRACKERNAME to URL field. This option is applied only when a new issue is to be filed. The default value is ABRT Server" Configuration file If not specified, CONFFILE defaults to /etc/libreport/plugins/mantisbt.conf. Configuration file lines should have PARAM = VALUE format. The parameters are: Login Login to MantisBT account. Password Password to MantisBT account. MantisbtURL MantisBT HTTP(S) address. (default: http://localhost/mantisbt) SSLVerify Use yes/true/on/1 to verify server’s SSL certificate. (default: no) Project Project issue field value. Useful if you needed different project
than specified in /etc/os-release ProjectVersion Version issue field value. Useful if you needed different project
version than specified in /etc/os-release CreatePrivate Create private MantisBT issue. (default: no)
Parameters can be overridden via $MantisbtPARAM environment variables. Formatting configuration files
Lines starting with # are ignored. Lines can be continued on the next line using trailing backslash. Format:
"%summary summary format" "section element1[,element2]..." The literal text line to be added to MantisBT Description or Additional information. Can be empty. (Empty lines are NOT ignored!)
Summary format is a line of text, where %element% is replaced by
text element's content, and [[...%element%...]] block is used only if
%element% exists. [[...]] blocks can nest. Sections can be:
- %summary: issue Summary format string.
- %attach: a list of elements to attach.
- %Additional info: issue Additional Information content.
- text, double colon (::) and the list of comma-separated elements. Description and Additional information MantisBT's fields:
All text, double colons (::) and lists of comma-separated elements which
are placed above the section '%Additional info::' in the configuration file are stored in the 'Description' field in MantisBT. All text etc. which are placed
under the '%Additional info::' are stored in the 'Additional information' field. For example: |:: comment | (Description) | | (Description) |Package:: package | (Description) | | (Description)
|%Additionalinfo:: |
|%reporter% | (Additional info) |User:: username,uid | (Additional info) | | (Additional info) |Directories:: root,cwd | (Additional info) Elements can be:
- problem directory element names, which get formatted as
: or : : : : - problem directory element names prefixed by "%bare",
which is formatted as-is, without "
:" and colons - %oneline, %multiline, %text wildcards, which select all corresponding elements for output or attachment
- %binary wildcard, valid only for %attach section, instructs to attach binary elements
- problem directory element names prefixed by "-", which excludes given element from all wildcards Nonexistent elements are silently ignored. If none of elements exists, the section will not be created. Integration with ABRT events
reporter-mantisbt can be used as an ABRT reporter. Example fragment for /etc/libreport/reportevent.conf:
# Report Python crashes EVENT=reportCentOSBugTracker analyzer=Python
reporter-mantisbt -d . -c /etc/libreport/plugins/mantisbt.conf OPTIONS
-d DIR Path to problem directory.
-c CONFFILE Path to configuration file.
-f Force reporting even if this problem is already reported.
-F CONFFORMATFILE Formatting file for new issues. Default: /etc/libreport/plugins/mantisbtformat.conf
-A CONFFORMATFILE Formatting file for duplicates. Default: /etc/libreport/plugins/mantisbtformatdup.conf
-t[ID] Upload FILEs to the already created issue on MantisBT site.
-h, duphash DUPHASH Search in MantisBT by abrt’s DUPHASH and print ISSUEID.
-r TRACKERNAME Set the last url from reporterto element which is prefixed with TRACKERNAME to URL field in MantisBT. ENVIRONMENT VARIABLES Environment variables take precedence over values provided in the configuration file. MantisbtLogin Login to MantisBT account. MantisbtPassword Password to MantisBT account. MantisbtMantisbtURL MantisBT HTTP(S) address. (default: http://localhost/mantisbt) MantisbtSSLVerify Use yes/true/on/1 to verify server’s SSL certificate. (default: no) MantisbtProject Project issue field value. Useful if you needed different project
than specified in /etc/os-release MantisbtProjectVersion Version issue field value. Useful if you needed different project
version than specified in /etc/os-release MantisbtCreatePrivate Create private MantisBT issue. (default: no) FILES /usr/share/libreport/conf.d/plugins/mantisbt.conf Readonly default configuration files. /etc/libreport/plugins/mantisbt.conf Configuration file. /etc/libreport/plugins/mantisbtformat.conf Configure formating for reporting. /etc/libreport/plugins/mantisbtformatdup.conf Configure formating for reporting duplicates. SEE ALSO reportevent.conf(5), mantisbtformat.conf(5), mantisbtformatdup.conf(5) AUTHORS · ABRT team
LIBREPORT 2.1.11.1 11/13/2018 REPORTER-MANTISBT(1)