The problem got resolved. The Sonar server was recently updated to only accept TLS v1.3. As task definition in [SonarQubePrepare@5] relied on node10, which lacks support for TLSv1.3, the connectivity with the server failed. As a temporary solution, we included a step before [SonarQubePrepare@5] to modify the task definition accordingly.
- bash: |
echo "Replacing Node version in SonarQube task"
find _tasks/SonarQube* -name 'task.json' -exec sed -i 's/Node10/Node16/g' {} \;
name: FixSonarQubeTask
workingDirectory: "/home/vsts/work"
PS: Could not manage to dynamically get workingDirectory path above, so had to hard code.
Tried, workingDirectory: “$(Agent.WorkFolder)” but with my build vm agent as Ubuntu, it did not work.