However after doing some more googling I figured that it is a legit issue & SonarSource Team is already aware of and has an open ticket for fixing it. I raised this issue in the SonarQube Google Group in an anticipation of getting response from someone who has faced this issue – Only after upgrading to SonarQube 6.5 and using the latest scanners, I started seeing these errors. This seem to be a bug with SonarQube latest scanner, since I had it working with the earlier versions. The Code Coverage does display in the TFS Build side though. In the Visual Studio Test build task, I have the Code Coverage Enabled checkbox checked, but I still do not get the code coverage details in SonarQube. It states that to import code coverage into SonarQube, add the Visual Studio Test build task after the build one and tick ‘ Code Coverage Enabled‘. I referred the SonarQube TFS Integration documentation link. T13:18:25.9706006Z WARNING: File is not under the project directory and cannot currently be analysed by SonarQube. Moving on to the issue of Code Coverage not being displayed in SonarQube, looking at the TFS Build logs, I get the below error message. SonarQube SQL Error – String or binary data would be truncated SonarQube Error – End of Central Directory record could not be found SonarQube 6.5 – Issues while configuring SQL Server Database If you are on the same journey and start seeing errors, make sure to check out my last few blog posts on SonarQube. I have been actively blogging about the issues I have been facing while setting up SonarQube in my project and also posting the resolutions. So now the question is how do I get Code Coverage to work? Everything works great end to end – with the only exception of Code Coverage. I have completed the integration with our TFS CI/CD Build. I have installed SonarQube 6.5 and have the server up and running.
0 kommentar(er)
