Trigger patterns should use checkout rules?

Avatar
Permanently deleted user
Created

Hello,

we have a configuration with the following checkout rules:
+:Tools/ConfigurationManagement => ./
+:CrossPath/branches/geolinux-2.1.0 => ./buildsystem

Then we have this trigger pattern:
+:buildsystem/packages/geolinux_2_0_HMC_1___ST*M.py

Now a file is checked into CrossPath/branches/geolinux-2.1.0:

added

http://teamcity.sbg.se/diffView.html?id=2957&vcsFileName=https%3a%2f%2fsvn.sbg.se%3a443%2fsvn%2fprojects%2fCrossPath%2fbranches%2fgeolinux-2.1.0%2fpackages%2fgeolinux_2_0_HMC_1_0_1_ST256M.py&personal=false



I would have thought this would trigger a build, but this change is placed in the Pending Changes tab. What are we doing wrong here?

Using TeamCity 4.5.5.

Thanks in advance!

Votes

0

Share

1 comment
Avatar
Yegor Yarko
Created

Daniel,

Sorry for such a big delay in replying, seems we overlooked the message for some time.

I can't reproduce the issue in the current TeamCity build. The issue could be already fixed: there were some probably related fixes in 5.0 and 5.1 EAP. Is upgrading an option for you?

You can probably try to change the checkout rule to "+:CrossPath/branches/geolinux-2.1.0 => buildsystem", this might help.

0

Please sign in to leave a comment.