![]() Save this temporary file and exit the editor.A path with spaces in it will generate an error like the following: Input Error: There is no file extension in "C:Program". IMPORTANT: The paths in the trigger cannot contain any spaces. Adjust the path to the Perl interpreter and the path to the file to make sure it points to on your server (wherever you put it). Note that this new line has a tab at the beginning."C:\path\to\your\perl.exe C:\path\to\your\ %changelist% %serverport% %client%" Perforce Version 2005.2 – you must specify the type of trigger as “change-commit” *: FogBugzTrigger change-commit //.Perforce Version 2004.2 – you must specify the type of trigger as “commit” *: FogBugzTrigger commit //.Perforce Version 2003.2 – all triggers are of type “submit”, no need to specify type: FogBugzTrigger //.The trigger looks slightly different depending on what version of Perforce you use: To add the FogBugz trigger you need to add a line to at the bottom of this file.(If it doesn’t, make sure the full path to p4 is in your path.) Type p4 triggers on the command line (or cmd window).We want to use a trigger to call the file every time any files are submitted in Perforce. Perforce will let you call an executable every time files are submitted (actually, just before the submission occurs). If you want to change this, look for the variable $CHANGELIST_ONLY and set it to 0. By default, the Perforce script sends changelists, not individual files (so you will see only one line in FogBugz for a changelist containing 40 files, instead of 40 lines). ![]() If you do NOT have Perforce passwords enabled, leave $P4PASSWORD blank. Please contact them at to pursue this option. Perforce passwords cannot be accessed from trigger scripts, so the good folks at Perforce will give you a free “background” or “automation” user for this purpose. Look for the variables $P4USERNAME and $P4PASSWORD and set them to the Perforce username and password you want to use. Put it in the directory that contains your Perforce server executable (for example, c:Program FilesPerforce).Follow the instructions above to setup the Perforce repository in FogBugz.Instructions for Perlĭownload and customize the trigger Perl script. 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. Getting Perforce to transmit changes to FogBugz Once it is installed and working with your Perforce repository, set the path to it in the New Repository dialog and click OK to complete the setup. In order to have FogBugz link to checked-in files directly from cases, you need to have P4Web installed. You can change this setting later by clicking the Edit icon next to the repository on the Admin -> Source Control page. Before you close the dialog, choose whether you want FogBugz to provide links to your check-ins. Download the script and follow the instructions below to set it up. Select the appropriate tab for the server Perforce runs on to use triggers, or DTG for the Perforce Defect Tracking Gateway (DTG). The resulting dialog contains a script for getting Perforce to transmit changes to FogBugz. In the resulting dialog, select Perforce as the type and give the repository a display name. To setup the repository in FogBugz, go to Admin (or Gear icon) -> Source Control. NOTE: If you are using FogBugz For Your Server and you are using the Perforce Defect Tracking Gateway (DTG), install and enable the Perforce DTG Integration plugin. Start by logging into FogBugz as an administrator. The starting point for setting up source control integration is to create the repository in FogBugz. Getting FogBugz to provide links to P4Web, the Perforce web client Setting up the repository in FogBugz Installing either trigger scripts (FogBugz On Demand, FogBugz On Site) or the Perforce Defect Tracking Gateway (FogBugz For Your Server) so that Perforce transmits changes to FogBugzĢ. There are two aspects to setting up FogBugz-Perforce integration:ġ. 5.2 Using Perforce DTG integration (FogBugz For Your Server).4 Getting FogBugz to provide links to P4Web, the Perforce web client.3.3 Instruction for Perforce DTG Integration (FogBugz For Your Server).3 Getting Perforce to transmit changes to FogBugz.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |