#Bugzilla interface full
The full pathname of the Mercurial repository. In addition to the usual Mercurial keywords, the Template to use when formatting comments. bugzilla.style The style file to use when formatting comments. bugzilla.fixresolution The resolution to set a bug to when marking fixed. bugzilla.fixstatus The status to set a bug to when marking fixed. The default expression matches Fixes 1234, Fixes bug 1234, It may also containĪ named group `` with a floating-point number giving the The bug IDs separated by non-digit characters. This must contain a "()" named group ` containing bugzilla.fixregexp Regular expression to match bug IDs for marking fixed in changesetĬommit message. Variations thereof, followed by an hours number prefixed by h or The default expression matches Bug 1234, Bug no. "()" group is assumed to contain the bug IDs, and work time is not If no named groups are present, the first It may also containĪ named group with a floating-point number giving the It must contain one "()" named group containing the bug
#Bugzilla interface update
MySQL access, Bugzilla 2.16 and up to but notīugzilla.regexp Regular expression to match bug IDs for update in changeset commit message. MySQL access, Bugzilla 2.18 and up to but not Values recognized are: restapi:īugzilla REST-API, Bugzilla 5.0 and later.
The given username or the user associated with the apikey in Bugzilla.Ĭonfiguration items common to all access modes: bugzilla.version Or an apikey specified in the configuration.
#Bugzilla interface password
Works on all supported Bugzilla versions.Īccess via the REST-API needs either a Bugzilla username and password User, the email associated with the Bugzilla username used to log intoīugzilla is used instead as the source of the comment. That the Mercurial user email is not recognized by Bugzilla as a Bugzilla User, so the comment appears to come from the Mercurial user. The From: address in the email is set to the email address of the Mercurial Marking bugs fixed requires Bugzilla 4.0 and later.Īccess via XMLRPC/email uses XMLRPC to query Bugzilla, but sendsĮmail to the Bugzilla email interface to submit comments to bugs. That the rights of that user are restricted in Bugzilla to the minimum Since theĬonfiguration must be readable by all Mercurial users, it is recommended
Only adding comments is supported in this access mode.Īccess via XMLRPC needs a Bugzilla username and password to be specified For these reasons this access mode is now consideredĭeprecated, and will not be updated for new Bugzilla versions goingįorward. MySQL user and password to have full access rights to the Bugzillaĭatabase. Permission to read Bugzilla configuration details and the necessary Must be run on the host with the Bugzilla install, and requires
This script runs as the user running Mercurial, Relies on a Bugzilla contrib script to send out bug change Writing directly to the database is susceptible to schema changes, and Writing directly to the Bugzilla database.Check data via the Bugzilla XMLRPC interface and submit bug change.Access via the Bugzilla XMLRPC interface.Bugs can also be marked fixed.įour basic modes of access to Bugzilla are provided: The bug references can optionally include an update for Bugzilla of the That refer to bugs by Bugzilla ID are seen. This hook extension adds comments on bugs in Bugzilla when changesets
0 kommentar(er)
