From e5b9f4fac1e56c36d72304c313432dc34edd80c9 Mon Sep 17 00:00:00 2001 From: "barnboy%trilobyte.net" <> Date: Fri, 4 Apr 2008 11:45:52 +0000 Subject: Updated Bugzilla Guide and README to fix bug 76156, bug 76841, and bug 26242. The README is now gutted, pointers to Guide. Also some new sections added, old ones fixed, and notes appended to deprecated sections I've not yet had the heart to remove. --- docs/en/xml/integration.xml | 141 +++++++++++++++----------------------------- 1 file changed, 48 insertions(+), 93 deletions(-) (limited to 'docs/en/xml/integration.xml') diff --git a/docs/en/xml/integration.xml b/docs/en/xml/integration.xml index 485a03dcd..74ec817f5 100644 --- a/docs/en/xml/integration.xml +++ b/docs/en/xml/integration.xml @@ -1,120 +1,75 @@ - + + -
+ + Integrating Bugzilla with Third-Party Tools -
+
Bonsai - - Bonsai is a web-based tool for managing - - - . Using Bonsai, administrators can control open/closed status of trees, - query a fast relational database back-end for change, branch, and comment - information, and view changes made since the last time the tree was - closed. Bonsai - also integrates with - . - + We need Bonsai integration information.
-
+
CVS + We need CVS integration information +
- CVS integration is best accomplished, at this point, using the - Bugzilla Email Gateway. - - Follow the instructions in this Guide for enabling Bugzilla e-mail - integration. Ensure that your check-in script sends an email to your - Bugzilla e-mail gateway with the subject of - [Bug XXXX], - and you can have CVS check-in comments append to your Bugzilla bug. If - you want to have the bug be closed automatically, you'll have to modify - the contrib/bugzilla_email_append.pl script. +
+ Perforce SCM + + Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack. + You can find the main project page at + + http://www.ravenbrook.com/project/p4dti. "p4dti" is now an officially + supported product from Perforce, and you can find the "Perforce Public Depot" + p4dti page at + http://public.perforce.com/public/perforce/p4dti/index.html. - - There is also a CVSZilla project, based upon somewhat dated - Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to - email. Check it out at: . + + Integration of Perforce with Bugzilla, once patches are applied, is fairly seamless. However, + p4dti is a patch against the Bugzilla 2.10 release, not the current 2.12 release. I anticipate + patches for 2.12 will be out shortly. Check the project page regularly for updates, or + take the given patches and patch it manually. p4dti is designed to support multiple defect + trackers, and maintains its own documentation for it. Please consult the pages linked + above for further information. - - Another system capable of CVS integration with Bugzilla is - Scmbug. This system provides generic integration of Source code - Configuration Management with Bugtracking. Check it out at: . + + Right now, there is no way to synchronize the Bug ID and the Perforce Transaction Number, or + to change the Bug ID to read (PRODUCT).bugID unless you hack it in. Additionally, if you + have synchronization problems, the easiest way to avoid them is to only put the bug + information, comments, etc. into Bugzilla, and not into the Perforce change records. + They will link anyway; merely reference the bug ID fixed in your change description, + and put a comment into Bugzilla + giving the change ID that fixed the Bugzilla bug. It's a process issue, not a technology + question. - -
- -
- - Perforce SCM - - You can find the project page for Bugzilla and Teamtrack Perforce - integration (p4dti) at: - - - . - p4dti - - is now an officially supported product from Perforce, and you can find - the "Perforce Public Depot" p4dti page at - - - . - - Integration of Perforce with Bugzilla, once patches are applied, is - seamless. Perforce replication information will appear below the comments - of each bug. Be certain you have a matching set of patches for the - Bugzilla version you are installing. p4dti is designed to support - multiple defect trackers, and maintains its own documentation for it. - Please consult the pages linked above for further information.
-
- Subversion - Subversion is a free/open-source version control system, - designed to overcome various limitations of CVS. Integration of - Subversion with Bugzilla is possible using Scmbug, a system - providing generic integration of Source Code Configuration - Management with Bugtracking. Scmbug is available at . +
+ Tinderbox + We need Tinderbox integration information
-
- Tinderbox/Tinderbox2 + - Tinderbox is a continuous-build system which can integrate with - Bugzilla - see - for details - of Tinderbox, and - to see it - in action. -
-
+ -- cgit v1.2.3-24-g4f1b