Home
About Perforce
Contact
Site Map
RSS
Triggers and Daemons
Scripting Perforce
This Knowledge Base section augments the Triggers and Daemons chapter of the Perforce System Administrator's Guide. More trigger examples can be found in the SAG or in the Perforce Public Depot.Articles
| Debugging Triggers | PROBLEM: How do I debug triggers? SOLUTION: This article provides a quick explanation of how triggers work, and outlines a few common usage pitfalls. The definitive reference for triggers is the ... |
| Enforce Workspace Naming | TASK: How do I enforce a naming convention on user workspaces that makes them readily identifiable? SOLUTION: Use a "form-out" trigger to check the name of a workspace specification before it is e... |
| Preventing Job Closure on Submit | PROBLEM: I would like to prevent jobs from being closed automatically when they are linked to a changelist being submitted. SOLUTION: The following shell script example finds any jobs attache... |
| Setting Up External Authentication Triggers | WARNING: Make sure you spell the trigger name correctly when adding the trigger with p4 triggers because a missp... |
| Trigger Form Output Changes in 2007.3 and Later | SUMMARY: Beginning with the 2007.3 version of the Perforce Server, output for triggers that succeed is passed to standard output. In previous server versions, only trigger output from failure wa... |
| Triggers and Passwords | TASK: Can I pass a user's password to a trigger? How do I authenticate commands issued by that trigger? SOLUTION: You cannot pass a specific user's password to a trigger as an argument. If your P... |
About This Page
|
Info & Tags
|
Links |
Privacy Policy