summaryrefslogtreecommitdiffstats
path: root/docs/html/scm.html
blob: 87dd195f1769614cc9f569445f271ef9a62bebc7 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
<HTML
><HEAD
><TITLE
>Perforce SCM</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.64
"><LINK
REL="HOME"
TITLE="The Bugzilla Guide"
HREF="index.html"><LINK
REL="UP"
TITLE="Integrating Bugzilla with Third-Party Tools"
HREF="integration.html"><LINK
REL="PREVIOUS"
TITLE="CVS"
HREF="cvs.html"><LINK
REL="NEXT"
TITLE="Tinderbox"
HREF="tinderbox.html"></HEAD
><BODY
CLASS="SECTION"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The Bugzilla Guide</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="cvs.html"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
>Chapter 5. Integrating Bugzilla with Third-Party Tools</TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="tinderbox.html"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECTION"
><H1
CLASS="SECTION"
><A
NAME="SCM"
>5.3. Perforce SCM</A
></H1
><P
>      Richard Brooksby created a Perforce integration tool for Bugzilla and TeamTrack.
      You can find the main project page at
      <A
HREF="http://www.ravenbrook.com/project/p4dti/"
TARGET="_top"
>	http://www.ravenbrook.com/project/p4dti</A
>.  "p4dti" 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 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.
    </P
><P
>      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.
    </P
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="cvs.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="tinderbox.html"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>CVS</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="integration.html"
>Up</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Tinderbox</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>