hg vcs triggers not triggering build
Turned on all diagnostic logs, vcs triggers don't always trigger the builds.
log excerpt below, There is 1 vcs root that is shared that checks every 4mins. The other snapshot dependency vcs root is not part of the trigger and checks every couple of days.
[2017-06-01 15:10:10,288] DEBUG [ggers Monitor 1] - ers.vcs.SingleBranchVcsTrigger - Build configuration: FullDebugTests, internal id=bt65}, branch: <default>, some VCS root is collecting changes, skip triggering
There is another error later on
WARN [ical executor 2] - jetbrains.buildServer.VCS - Error output produced by: "C:\program files\tortoisehg\hg.exe" --config ui.interactive=False pull --config extensions.progress= --config "progress.format=topic number" --config progress.delay=0 --config progress.assume-tty=True https://citeamcity:******@bitbucket.org/proj/release_9
teamcity.vcsTrigger.runBuildOnSameRevisionInEveryBranch is set to true
any ideas?
The VCS root has picked up the changes and is showing them as pending so don't know why it's saying "Some vcs root is collecting changes"
Is it the snapshot dependency vcs root, although I have filtered that out of the trigger:
VCS trigger rules:
+:root=vcsSharedroot:**
-:root=snapshotVCSroot:**
Branch filter:
+:<default>
Triggers one build per each VCS check-in
Using Mercurial and v10.0.0.5 (build 42677)
Please sign in to leave a comment.
Hi Michaelvonderbecke,
When you say that 'vcs triggers don't always trigger the builds', could you please elaborate on what builds are not triggered? Are they parts of the build chain (connected by snapshot dependencies)? If so, can you detail your build chain noting where the triggers are configured, please?
As to filtering out a root in the VCS trigger, it does not prevent TeamCity from collecting changes in this root, it just means that the detected changes will not trigger a build.