We have a CICD pipeline in Azure what always works with SonarCloud connection.
But, today we get the following error without changing the code:
Is there an update what we need to do? Or is there a bug in the connection?
Thanks for helping.
We’re experiencing the same issue. Looks like sonar pushed a breaking update. Can this be reverted/fixed please?
We are also experiencing this problem since this morning, we found the following line in the most recent succesful build:
[INFO] SonarQube version: 220.127.116.11993
And the first failed build without any changes to our code shows this:
[INFO] SonarQube version: 18.104.22.168029
We are having the same issue with this, nothing has changed in the Dockerfile but all of our builds are failing:
Running node -v before doing the sonar analysis returns a node version:
2024-01-17T12:00:16.9876517Z Step 30/77 : RUN node -v
2024-01-17T12:00:18.6495389Z ---> Running in 8324a1a3c308
We don’t have
node installed and have been getting the error message since always. However it never failed the analysis until today. Now the analysis fails and hence all builds fail.
Thanks for the reports. We’re currently investigating and will update here when we know more.
Feel free to add additional specifics here if they’re not already represented in the thread.
We’re reverting a change that was deployed at 10:00 CEST today. We expect deployment to be complete in ~2h.
We apologize for the inconvenience.
Ann & the SonarCloud team
We’ve reverted a change that caused the scanner to fail when nodejs is not found.
Please let us know if that resolves the issue.
Yes it resolve the issue.
Thank you for the update
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.