VCS trigger firing on branches with no relevant file changes

Avatar
Rokuyama
Created

We have multiple build configurations. Some are for non-mobile targets (e.g. web-server), and some are for mobile targets (iOS and Android). The mobile builds each have a VCS trigger with a path-specific trigger rule (e.g. +:ios/**) and branchFilter: +*.

Branches that contain no iOS or Android file changes are triggering the mobile builds. We are not sure why this is happening.

We want the VCS trigger to only fire for a branch if that branch itself contains relevant file changes. Is there a recommended way to configure this behavior?


 

Votes

0

Share

1 comment
Avatar
Tom Sun
Created

Hi,

The most likely cause is how VCS triggers historically handled merge commits. When a branch receives a merge, TeamCity may evaluate commits from the merged branch, not just the changes introduced by the merge itself. As a result, if the merged history contains commits under ios/** or android/**, the mobile trigger can fire on the target branch even when that branch only contains web-server changes.

This behavior is tracked in TW-93464. The fix is available in TeamCity 2025.07.2 and was backported to 2025.03.4.

Before recommending an upgrade, I'd like to confirm this is the issue you're seeing, as similar symptoms can also be caused by trigger/check-out rule configuration or other bugs. Could you please provide:

  1. Your TeamCity version and build number.
  2. One example of an unexpected trigger: the branch name, build ID, and a screenshot of the build's Changes tab.
  3. The corresponding teamcity-server.log and teamcity-vcs.log with the debug-triggers logging preset enabled (Administration → Diagnostics → Logging Preset).

If the logs confirm TW-93464, upgrading to 2025.07.2+ (or 2025.03.4+ on the 2025.03 line) should resolve the issue. Otherwise, the same information will help us identify the actual cause.

Large files can be uploaded via https://uploads.jetbrains.com/. Please let us know the exact id after the upload.

Best regards,
Tom

0

Please sign in to leave a comment.