False triggering of all build configurations instead of required

Answered

There is monorepo with bunch of microservices each of them located in their own directory and represented in Teamcity as projects with own build configurations. Each build configuration have VCS trigger pointing at service directory. Ex: +:/user/profile/** Everything is working perfectly and triggers are triggered on their own changes, except two cases. If we created branch from master or dev, made first commit (whatever file or folder), and then pushed it, Teamcity is triggered ALL build configurations. And the only second pushed commit triggered the right builds. A filling that Teamcity made checkout of new branch without checking any differences with default one.

The same situation with merge requests — new merge request triggered all build configurations.

 

My VCS settings:

Default branch: refs/heads/dev

Branch specification:

+:refs/heads/*
+:refs/merge-requests/*/head

 

0
2 comments

Hello muravlion,

What TeamCity version do you use? Do you have "teamcity.vcsTrigger.runBuildInNewEmptyBranch=true" parameter in build configuration or in parent projects configured? 

1
Avatar
Permanently deleted user

I'm using10.0.3 (build 42434) and magically your reference is works as I expected. I think this undocumented feature should be placed somewhere as checkbox.

0

Please sign in to leave a comment.