- versions used
- SonarQube v5.6.1 on-prem
- VSTS Marketplace extension v4.4.0
- error observed (wrap logs/code around triple quote ``` for proper formatting)
Our VSTS build definition hasn’t changed, but just today we started getting this error in our builds (we executed the build against the exact same changeset that succeeded two days ago):
2018-10-12T14:25:11.1839508Z "D:\a\1\s\src\Audit.Engagements.sln" (default target) (1) -> 2018-10-12T14:25:11.1839690Z "D:\a\1\s\src\Audit.Engagements\Audit.Engagements.sfproj" (default target) (2) -> 2018-10-12T14:25:11.1839864Z (SetRoslynCodeAnalysisProperties target) -> 2018-10-12T14:25:11.1840054Z D:\a\1\.sonarqube\bin\targets\SonarQube.Integration.targets(381,5): error MSB4044: The "GetAnalyzerSettings" task was not given a value for the required parameter "Language". [D:\a\1\s\src\Audit.Engagements\Audit.Engagements.sfproj]
Earlier in the build, the only other piece that looks different between the two logs is the following excerpt:
2018-10-12T14:24:51.3109154Z CreateProjectSpecificDirs: 2018-10-12T14:24:51.3109804Z Creating directory "D:\a\1\.sonarqube\conf\17". 2018-10-12T14:24:51.3110419Z SetRoslynCodeAnalysisProperties: 2018-10-12T14:24:51.3110567Z External issues are not supported on this version of SonarQube. SQv7.4+ is required. 2018-10-12T14:24:51.3135877Z CoreCompile:
I see that the build from two days ago ran v4.3.2 of the begin analysis SQ task, while today’s failed build is running the just-released v4.4.0.
.sfproj mentioned in the above log error is an Azure Service Fabric project. I guess that may be something that wasn’t tested during the development of v4.4.0, but this is a pretty serious issue. Unless there’s some workaround, this essentially means we have to disable all SonarQube analysis for this project.
For reference, our SonarQube server is installed on-prem, and running v5.6.1.
Is there a hotfix you can push to address this?