File: integration.html

package info (click to toggle)
bugzilla 2.16.7-7sarge2
links: PTS
area: main
in suites: sarge
size: 4,696 kB
ctags: 492
sloc: perl: 20,289; xml: 6,856; sh: 338; makefile: 211; python: 172
file content (286 lines) | stat: -rw-r--r-- 5,683 bytes
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML
><HEAD
><TITLE
>Integrating Bugzilla with Third-Party Tools</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
REL="HOME"
TITLE="The Bugzilla Guide - 2.16.7 Release"
HREF="index.html"><LINK
REL="UP"
TITLE="Administering Bugzilla"
HREF="administration.html"><LINK
REL="PREVIOUS"
TITLE="Upgrading to New Releases"
HREF="upgrading.html"><LINK
REL="NEXT"
TITLE="The Bugzilla FAQ"
HREF="faq.html"></HEAD
><BODY
CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide - 2.16.7 Release</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="upgrading.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="faq.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="section"
><H1
CLASS="section"
><A
NAME="integration"
>5.9. Integrating Bugzilla with Third-Party Tools</A
></H1
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="bonsai"
>5.9.1. Bonsai</A
></H2
><P
>Bonsai is a web-based tool for managing 
    <A
HREF="integration.html#cvs"
>CVS, the Concurrent Versioning System</A
>

    . 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  
    <A
HREF="integration.html#tinderbox"
>Tinderbox, the Mozilla automated build management system</A
>.
    </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="cvs"
>5.9.2. CVS</A
></H2
><P
>CVS integration is best accomplished, at this point, using the
    Bugzilla Email Gateway.</P
><P
>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 
    <SPAN
CLASS="QUOTE"
>"[Bug XXXX]"</SPAN
>, 
    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 <TT
CLASS="filename"
>contrib/bugzilla_email_append.pl</TT
> script.
    </P
><P
>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: 
    <A
HREF="http://homepages.kcbbs.gen.nz/~tonyg/"
TARGET="_top"
>&#13;    http://homepages.kcbbs.gen.nz/~tonyg/</A
>.
    </P
><P
>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: <A
HREF="http://freshmeat.net/projects/scmbug/"
TARGET="_top"
>http://freshmeat.net/projects/scmbug/</A
>.
    </P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="scm"
>5.9.3. Perforce SCM</A
></H2
><P
>You can find the project page for Bugzilla and Teamtrack Perforce
    integration (p4dti) at: 
    <A
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
>&#13;    http://www.ravenbrook.com/project/p4dti</A
>

    . 
    <SPAN
CLASS="QUOTE"
>"p4dti"</SPAN
>

    is now an officially supported product from Perforce, and you can find
    the "Perforce Public Depot" p4dti page at 
    <A
HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
TARGET="_top"
>&#13;    http://public.perforce.com/public/perforce/p4dti/index.html</A
>

    .</P
><P
>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.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="svn"
>5.9.4. Subversion</A
></H2
><P
>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 <A
HREF="http://freshmeat.net/projects/scmbug/"
TARGET="_top"
>http://freshmeat.net/projects/scmbug/</A
>.</P
></DIV
><DIV
CLASS="section"
><H2
CLASS="section"
><A
NAME="tinderbox"
>5.9.5. Tinderbox/Tinderbox2</A
></H2
><P
>We need Tinderbox integration information.</P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="upgrading.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="faq.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Upgrading to New Releases</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="administration.html"
ACCESSKEY="U"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>The Bugzilla FAQ</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>