After updating my build agent (CentOs) packages (it did an update of OpenJdk), it is not possible anymore to use the AzureDevops plugin Code Analysis (the prepare step do work).
I checked and adjusted the path and javaq_home variable for all users, without improvement.
I did the jdk update on another buildAgent: same, not working anymore.
Any idea ?
Error:
Starting: Run Code Analysis - community
==============================================================================
Task : Run Code Analysis - community
Description : Run scanner and upload the results to the SonarQube server.
Version : 4.8.0
Author : community-sonarsource
Help : This task is not needed for Maven and Gradle projects since the scanner should be run as part of the build.
[More Information](http://redirect.sonarsource.com/doc/install-configure-scanner-tfs-ts.html) - community
==============================================================================
/usr/bin/dotnet /var/vstsagent/_work/_tasks/SonarQubePrepareCommunityCommunity_33f55862-2cc1-4321-a3e5-6ff3d3f8600b/4.8.0/dotnet-sonar-scanner-msbuild/SonarScanner.MSBuild.dll end
SonarScanner for MSBuild 4.7.1
Using the .NET Core version of the Scanner for MSBuild
Post-processing started.
Calling the SonarQube Scanner...
Could not find 'java' executable in JAVA_HOME or PATH.
##[error]The SonarQube Scanner did not complete successfully
The SonarQube Scanner did not complete successfully
##[error]04:55:57.429 Post-processing failed. Exit code: 1
04:55:57.429 Post-processing failed. Exit code: 1
##[error]The process '/usr/bin/dotnet' failed with exit code 1
Finishing: Run Code Analysis - community
Environment variables just before the call to the scanner:
It doesn’t appear that you’re using the official SonarScanner for Azure DevOps, but instead some community fork?
If you’re doing this to circumvent some license restrictions – sorry, you aren’t going to be able to find help in this community. If you switch to the official Scanner for Azure DevOps, we’ll be happy to help.
So, i switched all my pipelines to the official version (i am not using the PR decoration part anyway so using an alternate version is not a benefit, no idea why i used this version in first place several years ago, maybe i was not able to make the official working so i tried randomly everything else…)
Starting: Run Code Analysis
==============================================================================
Task : Run Code Analysis
Description : Run scanner and upload the results to the SonarQube server.
Version : 5.4.0
Author : sonarsource
Help : Version: 5.4.0. This task is not needed for Maven and Gradle projects since the scanner should be run as part of the build.
[More Information](http://redirect.sonarsource.com/doc/install-configure-scanner-tfs-ts.html)
==============================================================================
/usr/bin/dotnet /var/vstsagent/_work/_tasks/SonarQubePrepare_15b84ca1-b62f-4a2a-a403-89b77a063157/5.4.0/dotnet-sonar-scanner-msbuild/SonarScanner.MSBuild.dll end
SonarScanner for MSBuild 5.5.3
Using the .NET Core version of the Scanner for MSBuild
Post-processing started.
Calling the SonarScanner CLI...
Could not find 'java' executable in JAVA_HOME or PATH.
##[error]The SonarScanner did not complete successfully
The SonarScanner did not complete successfully
##[error]02:56:33.534 Post-processing failed. Exit code: 1
02:56:33.534 Post-processing failed. Exit code: 1
##[error]The process '/usr/bin/dotnet' failed with exit code 1
Finishing: Run Code Analysis
and i have the very same error. This is puzzeling me as obviously it come from my agent setup, but all the values seems correct to me. The only borderline point is that i am using CentOs 7 hosts, that are now somehow old / deprecated.
By enabling the debug mode i was able to progress and notice that the task was not using the agent variables expected (even if defined correctly everywere, like in /etc/profile, .bashrc, forced by a shell step before the SQ step).
In theory the agent should refresh this value by taking it from the OS, and in my case it doesn’t…
After many attempts to have the JAVA_HOME correctly detected, i have finally an alternate solution, by setting in the user defined capabilities the JAVA_HOME_11_X64 variable.
