On this basis, Phabricator refused to implement some bugzilla features intended to make life easier for inexperienced users. Unlike Bugzilla, the Phabricator UI is primarily designed for software development and not for average non-technical users (according to upstream).Phabricator comes with many improvements over Bugzilla. In these cases you can follow the link to the task to learn about their current status. Some of the features described below are planned but not implemented today. Instead of trying to use Phabricator exactly how you used Bugzilla, we recommend you to get used to how Phabricator works. You can read a review of the migration in this blog post: Good bye Bugzilla, welcome Phabricator.Īll the Bugzilla reports have been migrated, and the process for reporting and managing bugs is basically the same. This extension doesn't need user interaction to run.Wikimedia has deprecated Bugzilla for bug reporting and replaced it by Phabricator. It is used with a collection of Mercurial repositories in /var/local/hg/repos/, with a web interface at in Usage This uses the Bugzilla at, logging in as user with password plugh. # Web root for browsing Mercurial repository. Strip=0 # Separator characters to strip from Mercurial repository path to get web root.īaseurl=. # Template to use when formatting comments. # Style file to use when formatting comments for Bugzilla. # Regular expression to match bug IDs to mark fixed in changeset commit message.įixstatus=RESOLVED # Bug status to use when marking bug fixed.įixresolution=FIXED # Bug resolution to use when marking bug fixed. # Regular expression to match bug IDs for update in changeset commit message.įixregexp=. See the documentation in hgrc(5), sections and. ![]() ![]() In addition, the Mercurial email settings must be configured. Usermap = filename # cfg file with "committer"="bugzilla user" info When using XMLRPC/email, you can specify mappings of Mercurial committers to Bugzilla users. User=bugs # Username to use to log into Bugzilla, default 'bugs'.įor full details of the available configuration settings, use the Mercurial help. Marking bugs fixed works on all supported Bugzilla versions.Ī minimal configuration using XMLRPC looks like this: In the event that the Mercurial user email is not recognized by Bugzilla as a Bugzilla user, the email associated with the Bugzilla username used to log into Bugzilla is used instead as the source of the comment. The From: address in the email is set to the email address of the Mercurial user, so the comment appears to come from the Mercurial user. ![]() Marking bugs fixed requires Bugzilla 4.0 and later.Īccess via XMLRPC/email uses XMLRPC to query Bugzilla, but sends email to the Bugzilla email interface to submit comments to bugs. Since the configuration must be readable by all Mercurial users, it is recommended that the rights of that user are restricted in Bugzilla to the minimum necessary to add comments. You need to configure access to your Bugzilla instance, and the method used for updating Bugzilla, which can be either XMLRPC or XMLRPC+email.Īccess via XMLRPC needs a Bugzilla username and password to be specified in the configuration. To configure the 'bugzilla' extension you add items to '' section of hgrc. # run bugzilla hook on every change pulled or pushed in here To use this extension, enable it in the configuration file (hgrc) like this: Marking bugs fixed may require Bugzilla 4.0 and later. This extension works with Bugzilla v3.4 and later. ![]() The bug references can optionally include an update for Bugzilla of the hours spent working on the bug. The comment is formatted using the Mercurial template mechanism. This hook extension adds comments on bugs in Bugzilla when changesets that refer to bugs by Bugzilla ID are seen.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |