We are using sonarqube 5.1.1 version and faced issues while analyzing .NET projects using sonar-runner.
As the recent update says, sonar-runner does not support .NET projects anymore, we have installed MSBuild.SonarQube.Runner-1.0 to analyze the same.
We are able to create dashboards for the .NET projects now but unit test cases and unit test coverage is missing.
Could you kindly help us here?
Please note that we have enterprise license and all the existing .NET projects in production environment use Visual studio 2010.
I have upgraded the dev instance to check the feasibility.
Related
I have upgraded my Teamcity build server to Teamcity 2020 and now I am not seeing .Net CLI runner (dotnet). I wasted a day try to fix this but still not resolved.
Does anyone have faced this issue?
The .NET cli plugin was renamed to .NET. In the common case TeamCity should convert all .NET cli steps to .NET steps automatically, but for the case when your had installed a custom version of .NET cli the conversion may not work. If you have few build configurations it is easier to do it manually. It is better to create a backup and to remove custom version of .NET cli before all operations. Otherwise you could create a ticket in the support.
I'm trying to set up a build configuration for an ASP.NET Core (built on .NET full framework 4.6.2) project.
I'm Using TeamCity Enterprise 2017.2.3 (build 51047)
The .NET Core SDK is installed on the build server, along with 4.6.2 of the .NET Framework.
I am getting the following Build Error Message:
... This project references NuGet package(s) that are missing on this computer. Use NuGet Package Restore to download them. For more information, see http://go.microsoft.com/fwlink/?LinkID=322105. The missing file is ..\packages\NETStandard.Library.2.0.3\build\netstandard2.0\NETStandard.Library.targets.
Anyone come across this error before?
I added the latest recommended Nuget exe (4.6.2) as well.
The build step upon which it is failing is a .NET CLI (dotnet) step.
I've set the Command to build
and the Projects to the Solution file.
Dotnet CLI is definitely installed and is version 2.1.300
Yeah update the build tools on the TeamCity server, you're probably using the latest Visual Studio version on your local machine but your build tools on the build server are slightly out of date, probably earlier than v15.5.
https://www.visualstudio.com/thank-you-downloading-visual-studio/?sku=BuildTools&rel=15
Also ensure that you have selected to add the .NET Core 2(+) build tools as they include the .NETStandard and aren't selected by default. See https://github.com/dotnet/standard/issues/458#issuecomment-323845208
one of our feature teams who is using SonarQube since long and they are now getting issues when they upgrade to VS 2017,To support SonarQube for scanning in VSTS build, we need the task updated with SonarQube 2.3 or higher to support along with VS 2017 for code analysis. May I know is there any work going on this when can we get the support for VS 2017?
Regarding SonarQube extension in VSTS, you can install SonarQube 3.0.2 version. (You need to update SonarQube extension if old version has already been installed in manage/admin extension page of you VSTS. https://XXX.visualstudio.com/_admin/_extensions)
After that, you can change 3.* version of SonarQube Scanner for MSBuild task in build or release.
Configuration:
Sonar: V. 5.1.1.
C#-PlugIn: V. 4.0
ReSharper-PlugIn: V. 2.0
ReSharper-InspectCode: V. 9.1.1
I'm getting the message "ReSharper plugin is running in deprecated mode" even though I have configured it as recommended here.
Any suggestions what I am doing wrong here?
Short answer The mode where R# is executed by the SonarQube analyzer is going to be deprecated starting from next week.
Long [and boring] answer
The re-use reports mode will replace it, where you invoke inspectcode.exe yourself and provide the path to its report to the SonarQube analyzer.
The R# 2.0 plugin has been released to work with the MSBuild SonarQube Runner 1.0 which will be released next week.
The MSBuild SonarQube Runner will replace the Visual Studio Boostrapper plugin.
Now, the re-use reports mode of the R# 2.0 plugin only works with the MSBuild SonarQube Runner, and cannot be used with the Visual Studio Bootstrapper. This explains why we have to wait until the MSBuild SonarQube Runner is released before being able to officially deprecate the current mode.
I'm trying to set up continuous integration at my current place of work. It's not something I've done before so I'm fairly certain that there will be a few steps I've not done or things I'm un-aware of.
I installed TeamCity Professional 7.1.3 on a build server (Windows Server 2008 R2). I've created a simple .NET application that has no database connections and only three NUnit tests. This app uses .NET framework 4.
I set up a build step using NUnit and received a number of errors but I've now resolved them, basically by installing the .NET framework on the build server.
I'm now adding an extra step using Visual Studio but TeamCity now displays the warning 'No enabled compatible agents for this build configuration'.
This question looks similar to mine:
What do I need to install a Visual Studio 2010 (sln)-compatible Build Agent in TeamCity? and it helped me solve the problems I had with NUnit but not for this current problem.
Is there something I've missed during my set-up? If I'm building and running tests with NUnit do I need to bother with this second step?
You installed the full framework, correct -- not just the client pieces? Here's a TeamCity forum post on how to resolve the Unmet requirements:DotNetFramework4.0_x86 exists compatibility error when you've previously installed the framework.