The Plastic SCM Trigger allows you to monitor a workspace for changes. A build is triggered when a file is checked in to the repository that the monitored workspace is pointing to.
General information on creating triggers can be found under the Triggers Reference topic.
When adding a Plastic SCM Trigger the following details are required:
Plastic SCM Workspace
Workspace to monitor - Provide the location of Plastic SCM workspace to monitor. This workspace will need to be configured to point to a repository server where changes are being made in order to trigger a build.
Plastic SCM Client Executable
Path to client executable - Specify the location of the Plastic SCM Client Executable (cm.exe) on the local machine.
Plastic SCM Trigger Options
Branch Monitoring Options
| • | Monitor all branches - Monitor all the branches under the workspace for changes. |
| • | Monitor specific branch - Only changes that occur within the specified branch will trigger a build. |
Update Workspace
| • | Update - Update the local workspace from the repository if changes have been detected. |
| • | Force - By default the update command will only update items that have been modified. The forced operation will create a new revision of all items regardless of whether a change has occurred or not. |
Exclude Files From Monitoring