Triggering before or after commands
Triggers of type command
allow you to configure
Helix server
to run a trigger before or after a given command executes. Generally, you
might want to execute a script before a command runs to prevent that
command from running; you might want to run a script after a command if
you want to connect its action with that of another tool or process.
You may use command type triggers with p4 push
and
p4 fetch
commands.
The following table describes the fields of the command
trigger.
Field | Meaning |
---|---|
|
The command to execute is specified in the
|
|
The The
For
additional information about the grammar of regular expressions,
see Examples of possible values:
To match a command name that is a substring of
another valid command, use the end-of-line
meta-character to terminate matching. For example, use
For additional information about path values with You cannot create a |
|
The trigger for Helix server
to run when the condition implied by Specify the command in a way that allows Helix server
to locate and run the command. The When your trigger script is stored in the depot, its path must
be specified in depot syntax, delimited by percent characters.
For example, if your script is stored in the depot as
|
Your search for returned result(s).