Closed NoxInmortus closed 11 months ago
Are you sure nothing changed in your build? For example, a plugin? The failure seems to be that whatever plugin is running the :asm:sonar
tasks requires Node.js. Node.js has never been installed on any of these images.
It seems we upgraded our Sonarqube instance from 8.9 to 9.9 between the two occurences, and it seems that now nodejs is now required (https://docs.sonarsource.com/sonarqube/9.9/setup-and-upgrade/lts-to-lts-release-upgrade-notes/):
JavaScript, TypeScript, and CSS analysis now requires Node.js 14.17+ (9.7)
In order to analyze Javascript, Typescript, and CSS code, Node.js 14.17+ must be installed on the machine running the scan. We recommend that you use the latest Node.js LTS, which is currently Node.js 18.
Nodejs is already installed on the Sonarqube server, does it means that the "machine running the scan" is the docker-gradle container ?
It sounds like it, yes. The SonarScanner CLI image has Node.js and Java on it, but not Gradle, so that image won't work (unless you change how you're scanning to use the scanner rather than the Gradle plugin).
Unfortunately, I can't think of a solution for this other than to create a new Docker image with this image as the base, and then copy the Node.js install stuff from somewhere like here.
Hello, I'm encountering an issue that may be caused by a change in the latest version of the docker image gradle:7.6-jdk11
Host specs:
The previous build dated from the 26th of June went fine, and I noticed that the tag has been updated 17 days ago.
here is the .gitlab-ci.yml used:
And here is the end of the job output (the previous job which succeed did not have any error nor failed):
I tried to run the job either with --info, --debug or --scan without more details. Any idea ?