1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
5
>Integrating Bugzilla with Third-Party Tools</TITLE
8
CONTENT="Modular DocBook HTML Stylesheet Version 1.79"><LINK
10
TITLE="The Bugzilla Guide - 3.0.4 Release"
11
HREF="index.html"><LINK
13
TITLE="Customizing Bugzilla"
14
HREF="customization.html"><LINK
16
TITLE="Customizing Who Can Change What"
17
HREF="cust-change-permissions.html"><LINK
19
TITLE="The Bugzilla FAQ"
20
HREF="faq.html"></HEAD
31
SUMMARY="Header navigation table"
40
>The Bugzilla Guide - 3.0.4 Release</TH
48
HREF="cust-change-permissions.html"
56
>Chapter 6. Customizing Bugzilla</TD
77
>6.5. Integrating Bugzilla with Third-Party Tools</A
88
>Bonsai is a web-based tool for managing
90
HREF="integration.html#cvs"
91
>CVS, the Concurrent Versioning System</A
94
. Using Bonsai, administrators can control open/closed status of trees,
95
query a fast relational database back-end for change, branch, and comment
96
information, and view changes made since the last time the tree was
100
HREF="integration.html#tinderbox"
101
>Tinderbox, the Mozilla automated build management system</A
114
>CVS integration is best accomplished, at this point, using the
115
Bugzilla Email Gateway.</P
117
>Follow the instructions in this Guide for enabling Bugzilla e-mail
118
integration. Ensure that your check-in script sends an email to your
119
Bugzilla e-mail gateway with the subject of
124
and you can have CVS check-in comments append to your Bugzilla bug. If
125
you want to have the bug be closed automatically, you'll have to modify
128
>contrib/bugzilla_email_append.pl</TT
132
>There is also a CVSZilla project, based upon somewhat dated
133
Bugzilla code, to integrate CVS and Bugzilla through CVS' ability to
134
email. Check it out at: <A
135
HREF="http://www.cvszilla.org/"
137
>http://www.cvszilla.org/</A
141
>Another system capable of CVS integration with Bugzilla is
142
Scmbug. This system provides generic integration of Source code
143
Configuration Management with Bugtracking. Check it out at: <A
144
HREF="http://freshmeat.net/projects/scmbug/"
146
>http://freshmeat.net/projects/scmbug/</A
156
>6.5.3. Perforce SCM</A
159
>You can find the project page for Bugzilla and Teamtrack Perforce
160
integration (p4dti) at:
162
HREF="http://www.ravenbrook.com/project/p4dti/"
164
>http://www.ravenbrook.com/project/p4dti/</A
173
is now an officially supported product from Perforce, and you can find
174
the "Perforce Public Depot" p4dti page at
176
HREF="http://public.perforce.com/public/perforce/p4dti/index.html"
178
>http://public.perforce.com/public/perforce/p4dti/index.html</A
183
>Integration of Perforce with Bugzilla, once patches are applied, is
184
seamless. Perforce replication information will appear below the comments
185
of each bug. Be certain you have a matching set of patches for the
186
Bugzilla version you are installing. p4dti is designed to support
187
multiple defect trackers, and maintains its own documentation for it.
188
Please consult the pages linked above for further information.</P
196
>6.5.4. Subversion</A
199
>Subversion is a free/open-source version control system,
200
designed to overcome various limitations of CVS. Integration of
201
Subversion with Bugzilla is possible using Scmbug, a system
202
providing generic integration of Source Code Configuration
203
Management with Bugtracking. Scmbug is available at <A
204
HREF="http://freshmeat.net/projects/scmbug/"
206
>http://freshmeat.net/projects/scmbug/</A
215
>6.5.5. Tinderbox/Tinderbox2</A
218
>Tinderbox is a continuous-build system which can integrate with
221
HREF="http://www.mozilla.org/projects/tinderbox"
223
>http://www.mozilla.org/projects/tinderbox</A
227
HREF="http://tinderbox.mozilla.org/showbuilds.cgi"
229
>http://tinderbox.mozilla.org/showbuilds.cgi</A
239
SUMMARY="Footer navigation table"
250
HREF="cust-change-permissions.html"
278
>Customizing Who Can Change What</TD
284
HREF="customization.html"
292
>The Bugzilla FAQ</TD
b'\\ No newline at end of file'