Trigger Path Specificity
Background: A developer commits to a ticket branch, Team City picks up the changes and runs a decompile (Access database, it's horrible), and then commits changes back to the branch.
I'm having a challenge with excluding commits made by our teamcity account, so a build is repeatedly triggered. Any idea what's going on?
Trigger rules:
+:.
-:user=svr_teamcity:.
Branch filter:
+:DEV-*
+:SW*
-:<default>
VCS username: svr teamcity <svr_teamcity@domain.com>
TeamCity user: svr teamcity (svr_teamcity)
TeamCity Enterprise 2018.1.1 (build 58406), Git VCS- Always checkout files on agent
Please sign in to leave a comment.
The problem turned out to be the VCS Username, Teamcity needs the full username listed, so my Trigger rules look like:
+:.
-:user=svr teamcity <svr_teamcity@domain.com>:.