My apologies for waking up an old thread, but did this feature change within the last few years? We have used Sonarqube for 6+ years now, and we configured our .Net repositories with SonarQube.Analysis.xml files based on the Sonarqube documentation at that time. Recently, we are noticing that the property settings from the file are not being used during the scans. We don’t want developers managing the sonarqube settings in the .csproj file, because we would have to be code owners to approve every change in the project file. Otherwise, the developers will just exclude every project from Sonarqube scanning, which violates security and internal audit requirements. This is a big set back if this xml file no longer works as it was documented.
Hi @Erik_Vickroy,
Thanks for your question.
Could you please give us more details about the problem?
- What scanner version did you use?
- What operating system do you use?
- Is the scanner running on a pipeline or in the local environment?
- What is your SonarQube version?
- How do you use the
SonarQube.Analysis.xmlfile? Is it the default one or do you use the/s:parameter? If you use the parameter, do you provide the full path? - What properties are set in the file but not considered?
Edit:
- Are you using one of the deprecated parameters (sonar.login or sonar.password)?