Setting up Perforce

There are two steps in setting up FogBugz-Perforce integration:

1. Installing either trigger scripts or the Perforce Defect Tracking Gateway so that Perforce transmits changes to FogBugz
2. Getting FogBugz to provide links to P4Web, the Perforce web client

Getting Perforce to transmit changes to FogBugz

We provide trigger scripts for Perforce in Perl or VBScript, depending on whether your Perforce server is running on Unix, where Perl is probably installed, or Windows, where VBScript is probably installed.

• See instructions for Perl
• See instructions for VBScript

If you have a Windows server which can access your Perforce server, you can use the Perforce Defect Tracking Gateway (DTG) instead of setting up trigger scripts. If you do this, FogBugz cases will appear in Perforce as Perforce Jobs and you can apply changelists to them directly.

• See instructions to set up Perforce DTG integration

Getting FogBugz to provide links to P4Web, the Perforce web client

In order to browse a Perforce repository, you need something that allows you to view file diffs and history logs from a web browser. With Perforce, you use P4Web, the Perforce Web Client.

Once that is installed and working with your Perforce repository, log onto FogBugz as an administrator and on the Settings | Site screen, go to the Main tab.

If you're using the DTG or a trigger script configured to send changelists instead of files (the default), enter the following:

• Under Source Control URL for logs, enter

http://path to P4Web:8080/@md=d&cd=//&c=6fI@/^R2?ac=10

• Under Source Control URL for diffs, enter 

http://path to P4Web:8080/@md=d&cd=//&c=6fI@/^R2?ac=10

If you've modified the trigger script to send files instead of changelists, enter the following:

• Under Source Control URL for logs, enter

http://path to P4Web:8080/@md=d&c=@^FILE?ac=22

• Under Source Control URL for diffs, enter 

http://path to P4Web:8080/@md=d&cdf=^FILE&ra=s&dw=wu&c=@^FILE?ac=19&rev1=^R1&rev2=^R2