Pre-tested commit should suppress subversion trigger

Hi,

I have a build configuration that has a subversion trigger, and this works as expected. However, if I do a pre-tested commit from within VS2008 (only commit if successful), the commit causes the subversion trigger to re-run the build(s). I've checked and there have been no other commits in the intervening period i.e. both the personal build and the subversion-triggered build have the same changes.

I would have thought that TeamCity should recognise the duplication and suppress the subversion triggered build.

Am I doing something wrong or is this expected behaviour?
Thanks
Akash

3 comments
Comment actions Permalink

Any suggestions?

0
Comment actions Permalink

Currently TeamCity triggers build even if a personal build with same commit has been run. Actually, since personal builds do not affect statistics and are visible to build owners only it is not so bad to have a regular build with your change recorded in the build history. If you are using personal builds all the time you can to avoid duplicate builds with help of VCS trigger rules: http://www.jetbrains.net/confluence/display/TCD4/Configuring+VCS+Triggers (consider using a rule with username)

You can also increase quiet period in the VCS trigger.

0
Comment actions Permalink

Thanks, the reason for triggering a build makes sense. I'll have a think about the VCS trigger rules, but I'd need to set one up for everyone in the team, and also there is the danger that someone forgets to use a pre-tested commit, meaning that the tests don't get run until the next pre-tested commit....

0

Please sign in to leave a comment.