Locked files after analysis

[Petr Maslan]

After completion of a build with SonarAnalysis (Windows agent) there stays 2 locked files (.sonarqube\bin\SonarScanner.MSBuild.Common.dll and .sonarqube\bin\SonarScanner.MSBuild.Tasks.dll) for a time (about 10 or 15 minutes). Files are locked by ".NET Core Host" process.

The consequence is if you run two builds in a short time, the second build every time fails.

We can fix it with waiting for release the files or kill ".NET Core Host" process at the agent or start a different build plan.

How we execute analysis: started by script (dotnet <path to SonarScanner.MSBuild.dll> begin /k:"project-key ...other keys"; end script executed by "SonarScanner for MSBuild - End Analysis" - same behavior is also SonarScanner for .NET Core - End Analysis".

Is possible to release all files after analysis is finnished?

[Michael Rüegg _Mibex Software_]

Hi,

AFAIK, our app doesn't hold a lock on these files. This must be done by the .NET Core host. The app just executes the dotnet command.

To be able to reproduce this issue, it would help us a lot if you could create a support ticket at https://support.mibexsoftware.com together with the Bamboo server logs with debug logging for the app enabled (please see here for more information: https://mibexsoftware.atlassian.net/wiki/spaces/MSS/pages/764215385/How+to+enable+debug+logging+for+Bamboo+apps).

Thanks in advance,

Michael (app vendor)