Exclude branch remote run from metric change failure

I have a branch remote run trigger set up, but when it fires, my build failure rule for number of tests since last successful build causes the remote runs to fail. It looks like it is always comparing the remote run branch to the default branch...rather than checking the last successful build in the branch.  The checks work correctly when building off a specific branch (using a branch specification) - but seems to just have the problem with the remote run branches (which I have had to explicitly exclude from the branch specifications so that the triggers will fire correctly).

Is this a known issue?  is there some additional logging I can turn on to see why teamcity is not comparing against the last successful build on the given branch?

I am using TeamCity 9

3 comments
Comment actions Permalink

Hi Nathan,

The last succesfull build from the same branch should be used. If there is no suitable build on the same branch, then build from default branch is used and the corresponding message is added to the build log. Please check that there is successfull build on the remote-run branch. Also do you see mesage in the build log?
Also since 9.0 the test counting logic has been changed.

0
Comment actions Permalink

Yes - the last successful build is used when it isn't a remote-run build.  When I do a remote-run build, it does not use the latest successful one.  The only  message in the build log is something to the effect of "Using build XXX for comparison" - where XXX is the last successful build for a non-remote-run branch, or the last successful build on the main branch - but it never catches the last successful build on the remote-run branch.

0
Comment actions Permalink

Sorry for delay. I've created the issue - https://youtrack.jetbrains.com/issue/TW-39583, please watch and vote for it.

0

Please sign in to leave a comment.