summaryrefslogtreecommitdiffstats
path: root/docs/html/integration.html
diff options
context:
space:
mode:
authorgerv%gerv.net <>2002-07-28 07:00:17 +0200
committergerv%gerv.net <>2002-07-28 07:00:17 +0200
commitd8caf6045d10344c431918128e3803ca497565f3 (patch)
tree1b2fbc50e442b6413a4ef0949e8ff7eed1df1361 /docs/html/integration.html
parenta9bb18746686c1bf5497e27f7ac2e12d0e3fc31a (diff)
downloadbugzilla-d8caf6045d10344c431918128e3803ca497565f3.tar.gz
bugzilla-d8caf6045d10344c431918128e3803ca497565f3.tar.xz
Merging new docs from 2.16 branch.
Diffstat (limited to 'docs/html/integration.html')
-rw-r--r--docs/html/integration.html165
1 files changed, 123 insertions, 42 deletions
diff --git a/docs/html/integration.html b/docs/html/integration.html
index 47447fbeb..9a7c1c432 100644
--- a/docs/html/integration.html
+++ b/docs/html/integration.html
@@ -9,14 +9,17 @@ CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
+REL="UP"
+TITLE="Administering Bugzilla"
+HREF="administration.html"><LINK
REL="PREVIOUS"
-TITLE="Bugzilla Security"
-HREF="security.html"><LINK
+TITLE="Upgrading to New Releases"
+HREF="upgrading.html"><LINK
REL="NEXT"
-TITLE="Bonsai"
-HREF="bonsai.html"></HEAD
+TITLE="The Bugzilla FAQ"
+HREF="faq.html"></HEAD
><BODY
-CLASS="chapter"
+CLASS="section"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
@@ -42,7 +45,7 @@ WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
-HREF="security.html"
+HREF="upgrading.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -50,13 +53,13 @@ ACCESSKEY="P"
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
-></TD
+>Chapter 5. Administering Bugzilla</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
-HREF="bonsai.html"
+HREF="faq.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -66,38 +69,112 @@ ACCESSKEY="N"
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
-CLASS="chapter"
+CLASS="section"
><H1
+CLASS="section"
><A
-NAME="integration">Chapter 5. Integrating Bugzilla with Third-Party Tools</H1
+NAME="integration">5.9. Integrating Bugzilla with Third-Party Tools</H1
><DIV
-CLASS="TOC"
-><DL
-><DT
-><B
->Table of Contents</B
-></DT
-><DT
->5.1. <A
-HREF="bonsai.html"
->Bonsai</A
-></DT
-><DT
->5.2. <A
-HREF="cvs.html"
->CVS</A
-></DT
-><DT
->5.3. <A
-HREF="scm.html"
->Perforce SCM</A
-></DT
-><DT
->5.4. <A
-HREF="tinderbox.html"
->Tinderbox/Tinderbox2</A
-></DT
-></DL
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="bonsai">5.9.1. Bonsai</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</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 have your check-in script include an @resolution field, you can even
+ change the Bugzilla bug state.</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
+></DIV
+><DIV
+CLASS="section"
+><H2
+CLASS="section"
+><A
+NAME="scm">5.9.3. Perforce SCM</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="tinderbox">5.9.4. Tinderbox/Tinderbox2</H2
+><P
+>We need Tinderbox integration information.</P
></DIV
></DIV
><DIV
@@ -116,7 +193,7 @@ WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
-HREF="security.html"
+HREF="upgrading.html"
ACCESSKEY="P"
>Prev</A
></TD
@@ -134,7 +211,7 @@ WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
-HREF="bonsai.html"
+HREF="faq.html"
ACCESSKEY="N"
>Next</A
></TD
@@ -144,17 +221,21 @@ ACCESSKEY="N"
WIDTH="33%"
ALIGN="left"
VALIGN="top"
->Bugzilla Security</TD
+>Upgrading to New Releases</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
->&nbsp;</TD
+><A
+HREF="administration.html"
+ACCESSKEY="U"
+>Up</A
+></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
->Bonsai</TD
+>The Bugzilla FAQ</TD
></TR
></TABLE
></DIV