How to apply filters to triggers

Some days ago, we published a new update to the Triggers guide about how filters work with triggers.

As you may already know, the trigger system in Plastic SCM allows the execution of user commands at certain points in the client or server execution workflow, in the form of shell scripts or any other operating system executable.

Among others, the trigger system in Plastic SCM will allow the developer or administrator to perform the following tasks:

• Enforce branch creation policies like naming conventions or making sure that branch names always refer to a certain associated task.
• Introduce before-checkin rules to enforce coding standards or create formatting rules.
• Enforce that comments are introduced on checkin.

Triggers are created from the command line client:

cm trigger create {type} {name} {script}
  [--position=value]
  [--filter=filter-value]
  [--server=server:port]

and you must use the --filter option if you want to restrict when the trigger executes.

This blogpost is a summary of the explanation and examples that we included in the Triggers guide.