Problems with Build trigger, commits during mvn release:prepare triggers next build

We want teamcity to build a new release everytime a developer commits a change in our release branch. Unfortunately the commits executed during the release run trigger the next build.
We tried several variations of VCS Trigger rules, but nothing seems to help.

We tried to filter on the user name "appadm"
we tried to filter on the comment "maven-release-plugin"
we tried a combination of both

we initially had a quiet period of 1800

but anyway the build is triggerd of commit like :
Screen shot 2011-07-07 at 5.32.43 PM.png
This smells like a bug to us. We are using TeamCity Enterprise 6.0.2 (build 15857)

Our VCS Settings
Screen shot 2011-07-07 at 5.26.07 PM.png
VCS root (slightly anonymized)
Screen shot 2011-07-07 at 5.27.09 PM.png
Screen shot 2011-07-07 at 5.27.21 PM.png
and the build trigger infos :
Screen shot 2011-07-07 at 5.27.47 PM.png
Screen shot 2011-07-07 at 5.27.54 PM.png
we also tried
-:user=appadm:**/*

Please help if you have any idea whats wrong.

Thanks in advance, Oli

2 comments
Comment actions Permalink

Oliver,

Sorry for the delay in replying.

As far as I understand your setup any of the following VCS triggering rules should work:

-:user=appadm:**
-:comment=maven-release-plugin:**

Default **/* pattern is confusing since it means "all files except for those directly under root directory". I filed an issue to fix this confusion some time ago: TW-17613.

0
Comment actions Permalink

Thanks, that fixed the problem.

0

Please sign in to leave a comment.