p4 triggers
Create or display a list of scripts to be run conditionally whenever changelists are submitted, forms are updated, when integrating Perforce with external authentication or archive mechanisms, when rotating journals, or when pushing or fetching content to and from a remote depot.
Syntax conventions
p4 [g-opts] triggersp4 [g-opts] triggers -op4 [g-opts] triggers -i
Description
Helix server triggers are user-written scripts or programs that are called by a
Helix server whenever certain operations (such as changelist submission or
changes to forms) are performed. If the script returns a value of
0, the operation continues; if the script returns any other
value, the operation fails.
The p4 triggers command includes three variants:
- With no options specified, the command invokes the default editor to allow the user to specify one or more trigger definitions.
- The
-ioption specifies that the user use standard input to specify one or more trigger definitions. - The
-ooption displays the trigger definitions currently stored in the trigger table.
A trigger definition contains four fields that specify the name of the trigger, the type of event that should trigger the execution of the script, the location of the script, and other trigger type-dependent information. When the condition specified in a trigger definition is satisfied, the associated script or program is executed.
For detailed information about writing triggers and trigger definitions, see "Using triggers to customize behavior" in the Helix Core Server Administrator Guide.
Options
|
|
Read the trigger table from standard input without invoking the editor. |
|
|
Write the trigger table to standard output without invoking the editor. |
|
|
See Global options. |
Usage Notes
| Can File Arguments Use Revision Specifier? | Can File Arguments Use Revision Range? | Minimal Access Level Required |
|---|---|---|
|
N/A |
N/A |
|
Related Commands
|
To obtain information about the changelist being submitted |
|
|
To aid daemon creation |
