VCS Trigger and Trigger Rules
Hi,
TeamCity 2017.1 (build 46533)
Plastic SCM version 5.4.16.814 Doobie Brothers - China Grove
I have configured an include Trigger rule in TeamCity triggers to include changes from a particular VCS root and a specific file path.
+:root=testbuild_VCSTestBuilds:Utilities/**
The rule should only trigger a build if it detects changes within the utilities folder and ignore any changes in any of the other folders.
Having set this rule once a change is made it is recognized as a pending change - but no build fires off.
Have I done something wrong or is there an issue between TeamCity and Plastic SCM
Thanks in advance,
PJ
Please sign in to leave a comment.
Hi Paul, and sorry for the delay.
While normally the triggers are triggered by TeamCity, not the third party plugin, when trigger rules are included, it's the plugin who reports some of the information about the changes, so it's possible the issue is related to the Plastic SCM plugin itself.
Do you have checkout rules in the VCS Root? Also, you might try activating debug-vcs on the diagnostics page and sending a new check in. That would log details about the changes, showing more information on where the issue actually resides.