3578bee4a5
be used for 2.14 documentation due to inconsistencies. git-svn-id: svn://10.0.0.236/trunk@100820 18797224-902f-48f8-a5cc-f745e15eee43
78 lines
2.8 KiB
XML
78 lines
2.8 KiB
XML
<!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN" > -->
|
|
|
|
<!-- Keep these tools listings in alphabetical order please. -MPB -->
|
|
|
|
<chapter id="integration">
|
|
<title>Integrating Bugzilla with Third-Party Tools</title>
|
|
|
|
<section id="bonsai">
|
|
<title>Bonsai</title>
|
|
<para>We need Bonsai integration information.</para>
|
|
</section>
|
|
|
|
<section id="cvs">
|
|
<title>CVS</title>
|
|
<para>CVS integration is best accomplished, at this point, using the Bugzilla Email Gateway.</para>
|
|
</section>
|
|
|
|
<section id="scm">
|
|
<title>Perforce SCM</title>
|
|
<para>
|
|
You can find the project page for Bugzilla and Teamtrack Perforce integration at:
|
|
<ulink url="http://www.ravenbrook.com/project/p4dti/">
|
|
http://www.ravenbrook.com/project/p4dti</ulink>. "p4dti" is now an officially
|
|
supported product from Perforce, and you can find the "Perforce Public Depot"
|
|
p4dti page at <ulink url="http://public.perforce.com/public/perforce/p4dti/index.html">
|
|
http://public.perforce.com/public/perforce/p4dti/index.html</ulink>.
|
|
</para>
|
|
<para>
|
|
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.
|
|
</para>
|
|
<para>
|
|
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.
|
|
</para>
|
|
</section>
|
|
|
|
<section id="tinderbox">
|
|
<title>Tinderbox</title>
|
|
<para>We need Tinderbox integration information</para>
|
|
</section>
|
|
|
|
</chapter>
|
|
|
|
|
|
|
|
|
|
<!-- Keep this comment at the end of the file
|
|
Local variables:
|
|
mode: sgml
|
|
sgml-always-quote-attributes:t
|
|
sgml-auto-insert-required-elements:t
|
|
sgml-balanced-tag-edit:t
|
|
sgml-exposed-tags:nil
|
|
sgml-general-insert-case:lower
|
|
sgml-indent-data:t
|
|
sgml-indent-step:2
|
|
sgml-local-catalogs:nil
|
|
sgml-local-ecat-files:nil
|
|
sgml-minimize-attributes:nil
|
|
sgml-namecase-general:t
|
|
sgml-omittag:t
|
|
sgml-parent-document:("Bugzilla-Guide.sgml" "book" "chapter")
|
|
sgml-shorttag:t
|
|
sgml-tag-region-if-active:t
|
|
End:
|
|
-->
|