diff options
author | justdave%syndicomm.com <> | 2004-02-05 13:49:08 +0100 |
---|---|---|
committer | justdave%syndicomm.com <> | 2004-02-05 13:49:08 +0100 |
commit | 11945a73c631bedbcf8daaba531964c3fc2d6333 (patch) | |
tree | 6c23288dd801bd8a1bf9ad548eb9a4e82cd24eef /docs/html/integration.html | |
parent | cfc778d1fc757e022c0755ccc5ecd430790ce8be (diff) | |
download | bugzilla-11945a73c631bedbcf8daaba531964c3fc2d6333.tar.gz bugzilla-11945a73c631bedbcf8daaba531964c3fc2d6333.tar.xz |
- Remove html, txt, and pdf directories from CVS
- makedocs.pl now creates said directories when building the docs
The idea here is that it's useless to have compiled stuff in CVS. The website will now auto-build the docs upon changes to
the xml directory.
Diffstat (limited to 'docs/html/integration.html')
-rw-r--r-- | docs/html/integration.html | 272 |
1 files changed, 0 insertions, 272 deletions
diff --git a/docs/html/integration.html b/docs/html/integration.html deleted file mode 100644 index 2e8d18ae3..000000000 --- a/docs/html/integration.html +++ /dev/null @@ -1,272 +0,0 @@ -<HTML -><HEAD -><TITLE ->Integrating Bugzilla with Third-Party Tools</TITLE -><META -NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+ -"><LINK -REL="HOME" -TITLE="The Bugzilla Guide - 2.17.7 - Development Release" -HREF="index.html"><LINK -REL="UP" -TITLE="Customising Bugzilla" -HREF="customization.html"><LINK -REL="PREVIOUS" -TITLE="MySQL Bugzilla Database Introduction" -HREF="dbdoc.html"><LINK -REL="NEXT" -TITLE="Using Bugzilla" -HREF="using.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.17.7 - Development Release</TH -></TR -><TR -><TD -WIDTH="10%" -ALIGN="left" -VALIGN="bottom" -><A -HREF="dbdoc.html" -ACCESSKEY="P" ->Prev</A -></TD -><TD -WIDTH="80%" -ALIGN="center" -VALIGN="bottom" ->Chapter 4. Customising Bugzilla</TD -><TD -WIDTH="10%" -ALIGN="right" -VALIGN="bottom" -><A -HREF="using.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -></TABLE -><HR -ALIGN="LEFT" -WIDTH="100%"></DIV -><DIV -CLASS="section" -><H1 -CLASS="section" -><A -NAME="integration" -></A ->4.6. Integrating Bugzilla with Third-Party Tools</H1 -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="bonsai" -></A ->4.6.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" -></A ->4.6.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 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" ->http://homepages.kcbbs.gen.nz/~tonyg/</A ->. - </P -></DIV -><DIV -CLASS="section" -><H2 -CLASS="section" -><A -NAME="scm" -></A ->4.6.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" ->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" ->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" -></A ->4.6.4. Tinderbox/Tinderbox2</H2 -><P ->Tinderbox is a continuous-build system which can integrate with - Bugzilla - see - <A -HREF="http://www.mozilla.org/projects/tinderbox" -TARGET="_top" ->http://www.mozilla.org/projects/tinderbox</A -> for details - of Tinderbox, and - <A -HREF="http://tinderbox.mozilla.org/showbuilds.cgi" -TARGET="_top" ->http://tinderbox.mozilla.org/showbuilds.cgi</A -> to see it - in action.</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="dbdoc.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="using.html" -ACCESSKEY="N" ->Next</A -></TD -></TR -><TR -><TD -WIDTH="33%" -ALIGN="left" -VALIGN="top" ->MySQL Bugzilla Database Introduction</TD -><TD -WIDTH="34%" -ALIGN="center" -VALIGN="top" -><A -HREF="customization.html" -ACCESSKEY="U" ->Up</A -></TD -><TD -WIDTH="33%" -ALIGN="right" -VALIGN="top" ->Using Bugzilla</TD -></TR -></TABLE -></DIV -></BODY -></HTML ->
\ No newline at end of file |