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 in need of one or more responsible, knowledgeable curators.
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.
Until a curator is found, you may request to have your submitted changes integrated into this project by emailing Perforce staff at info@perforce.com. |
Depot Browsers | Back to Table of Contents |
Conversion Scripts | Back to Table of Contents |
Review Daemons | Back to Table of Contents |
Pre-Submit Triggers | Back to Table of Contents |
Script Name | Status* | |
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".) | |
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. |
*How to interpret the "Status" field:
Diffing and Merging | Back to Table of Contents |
Defect Tracking | 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/laura_wingerd/perforce/utils/index.html#5 $ in the Perforce Public Depot. |
Back to Table of Contents |