Some builds are not handled by the plugin

[Sharken03]

Problem encountered with TeamCity 2018.2.2 and the bundled Auto-assigner plugin.

A build step is running tests using nunit3-console.exe with the '-teamcity' argument. After the completion of the build step, there are a number of test failures reported by nunit3-console.exe.

However we never see any logging of the buildid in the Auto-assigner logs, there is plenty of logging from other builds. Since the builds in question is not referenced in the logs, it is hard to give further information. Note that this is the same build server that encountered the issue in #45.

The teamcity-server.log shows this information when the build finishes: [2019-01-29 11:29:47,396] INFO - jetbrains.buildServer.SERVER - Build finished received for build: #798 {build id=69708, buildTypeId=Project_Full} [2019-01-29 11:29:47,396] INFO - rverSide.impl.RunningBuildImpl - The calculated statistic value 'serverSideBuildFinishing' is less than 0 (-21) for the build:#798 {build id=69708, buildTypeId=Project_Full} [2019-01-29 11:29:47,445] INFO - ndexer.EventBasedBuildsIndexer - Indexing finishing build: #798 {build id=69708, buildTypeId=Project_Full} [2019-01-29 11:29:47,504] INFO - de.impl.history.DBBuildHistory - Created build history entry; build id: 69708, finish date: 2019-01-29 11:29:47.417 [2019-01-29 11:29:47,509] INFO - tbrains.buildServer.ACTIVITIES - Finished build Project / Full {id=Project_Full, internal id=bt152} #798 {promotion id=69708, branch=topic/dev, agent="tcbuildagent-05" {id=9}, triggered by "Mercurial" (##vcsName='mercurial' type='vcs'). Started 2019-01-29 09:42:49.108, finished. Status "FAILURE 'Tests failed: 10 (9 new), passed: 36204, ignored: 165'"}

[rugpanov]

I will try to reproduce the issue

[Sharken03]

Will try to add more details, but its a bit hard to know if its relevant or not. I can add that it was a build on a branch that is not the default branch. Three builds on that branch seem to be connected like this:

• The first build in the chain had 1 test error.
• That build just before the one i linked above, still had the same test error as the first build.
• The third build in the chain (the one linked in this issue) also had that same test error, but also 9 new test errors.

None of these builds were ever investigated by the plugin, while it seems that all builds on the Default Branch have been investigated by the plugin. So initially i would say it has something to do with Default Branch vs. other branches.

[Sharken03]

I think this one can be closed, as it is handled by #34 and the "teamcity.investigationsAutoAssigner.enableFeatureBranchesSupport" parameter, which hopefully is included with 2018.2.2.

My bad for not remembering that one.