About This Project | Back to Table of Contents |
| Content | The Perforce Utilities Project is a collection of programs and scripts that integrate Perforce with a variety of software development tools and environments, and/or provide alternative interfaces to the Perforce SCM system. |
| Curator |
This project is maintained by Perforce staff, with individual
curators as shown below.
Eventually we'll split these utilities up into separate projects,
depending on their activity and growth. If you have a particular
interest in any or all of this project, and would like
to volunteer as a curator, please email us.
If you would like to contribute to one of the categories that does not have a curator yet, you may request to have your submitted changes integrated into this project by emailing Perforce staff at opensource@perforce.com. |
Depot Browsers | Back to Table of Contents |
NOTE: Security problems have been found with the P4DB implementation. Refer to this Bugtraq notification for more details.
Conversion Scripts | Back to Table of Contents |
Both the VSS and PVCS conversion projects are curated by Robert Cowham.
Review Daemons | Back to Table of Contents |
Triggers | Back to Table of Contents |
auth-check
and auth-set. See the
Perforce System Administrator Guide for additional details.
Below are examples of the two new trigger types:
| Script Name | Trigger Type | |
| p4authenticate.pl | auth-check | Simple example of LDAP authentication written in Perl. |
| p4authenticate.c | auth-check | Simple example of LDAP authentication written in C. |
| testpass.pl | auth-check | Test trigger to confirm authentication check is working. |
delete trigger type
was added. Examples of all of these trigger types can be found in the
Perforce System Administrator Guide.
submit).
Unless otherwise noted, the trigger scripts below were written and contributed byJeff Bowles.
| Script Name | |
| Jobs.pl | Example trigger to enforce a rule "submissions must be associated with a job.". |
| Jobs.sh | Similar to above, but contributed by Wes Peters and written in Unix "shell". Takes a different approach to the problem, running "p4 fixes" to determine whether you're fixing something with this submission. |
| CheckC.pl |
A script to notice when you're creating new files (or integrating to a new
branch) and the directory name you're writing the [new] file to isn't the
same case as an existing directory name. (For example, if "//depot/x/y/z.c" exists, this won't allow you to create a file named "//depot/X/Y/one.c".) WARNING: This trigger can significantly affect performance. |
| Pairs.pl | Example trigger to enforce a rule "files of suffix .x/.y need to be checked in as pairs". |
| Binary.pl | Example trigger to enforce a rule "submissions of .gif must binary files and .sh files should be text and...." |
| simple.cmd | Classroom example of writing a trigger using the Windows/NT command shell, a.k.a. "a .cmd script". (It checks that "Bug:" is included in the change description.) Doesn't do a lot, but gets the idea across. |
Diffing and Merging | Back to Table of Contents |
Compatibility Aids | Back to Table of Contents |
Miscellany | Back to Table of Contents |
|
Copyright © 1998, 1999 Perforce Software |
You're browsing a file stored as$Id: //guest/perforce_software/utils/index.html#28 $in the Perforce Public Depot. |
Back to Table of Contents |