When you create coverage reports for your .NET projects you have the ability to use the native logger mechanism in order to export a trx report with your results.
An example of this native functionality can be found below as the logger parameter is used along with dotnet test.
dotnet test keyvault.sln --logger "trx;logfilename=mytests.trx"
However if you try to upload this trx file in a sonarqube in order to get your coverage report result, this will fail with the below error message.
WARN: Could not import coverage report ‘.\Keyvault_MI_Pod\Tests\TestProject1\TestResults\mytests.trx’ because ‘Only dotCover HTML reports which start with “” are supported.’. Troubleshooting guide: https://community.sonarsource.com/t/37151
Using the below sonarqube documentation page you will find all the available methods that are supported for the coverage reporting. When you need to upload your coverage results in sonarqube you will need to use a tool from the list and upload the file that this tool generates.
.NET test coverage (sonarsource.com)
In my case I will use dotCover and create the relevant report file.
In the teamcity task (begin analysis) you will need to add in the additional parameters where you export your report.
Then in the pipeline you will need to add the dotnet test task as shown from the documentation.
dotnet dotcover test --dcReportType-HTML
In the finish task you will see the coverage report type is now compatible and can be parsed from sonarqube.
Finally you will have your coverage report inside sonarqube.
Sonarqube is a self-managed, automatic code review tool that systematically helps you deliver clean code. SonarQube integrates into your existing workflow and detects issues in your code to help you perform continuous code inspections of your projects. In this article we will examine how to integrate it with Teamcity in order to scan our workflows during build.
First you will need to install the sonar runner for your teamcity installation. You should go in the administration tab
and then plugins
Then browse plugin directory and install the sonar runner.
After that you should go in root project and integrate sonar tool with teamcity.
Press add a new server and provide Name, URL and the Token. Token can be retrieved from your sonar installation. Under Administration select security and create a new token with an expiry date.
Finally you can create a new build definition and use the sonar scanner plugin.
I was trying to validate if a custom value that I overrode on a helm deployment was correct. In order to override a value in values.yaml you will need to pass the set flag as shown below.
helm upgrade --install -n sonarqube sonarqube sonarqube/sonarqube --set persistence.enabled=true
In the above installation command I override the persistence.enabled value to true instead of false that is by default.
First of all you will need to get the release name of the helm chart that you deployed. You can find this information by
helm list --all -n namespace
After finding the name of the release you will need to use the get command in order to get values.
helm -n sonarqube get values sonarqube -n sonarqube
This option will persist the Elasticsearch indexes in a Persistent Volume, but with regular killing operations by the Kubernetes Cluster, these indexes can be corrupted. By default, persistency is disabled in the Helm chart.
Deploy SonarQube on Kubernetes (sonarsource.com)