You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 9, 2023. It is now read-only.
We are seeing intermittent failures while running sonar scan on our Jenkins (UNIX) machines.
Before kicking off the scan, we run these custom commands
ls -la /home/jenkins | grep sonar
mkdir -p /home/jenkins/.sonar
ln -fs /opt/sonar /home/jenkins/.sonar/native-sonar-scanner || echo "link already exists, skipping link creation"
ls -la /home/jenkins/.sonar
And we kickoff the scan via npm action defined in the package.json.
npm run sonar-scan
While running the above command, the sonar scanner is failing occasionally with the following error.
[19:53:10] Starting analysis...
[19:53:10] Checking if executable exists: /home/jenkins/.sonar/native-sonar-scanner/sonar-scanner-4.5.0.2216-linux/bin/sonar-scanner
[19:53:10] Could not find executable in "/home/jenkins/.sonar/native-sonar-scanner".
[19:53:10] Proceed with download of the platform binaries for SonarScanner...
[19:53:10] Creating /home/jenkins/.sonar/native-sonar-scanner
/home/jenkins/workspace/**********/**********/node_modules/sonarqube-scanner/node_modules/mkdirp/lib/mkdirp-manual.js:59
throw er
^
Error: EEXIST: file already exists, mkdir '/home/jenkins/.sonar/native-sonar-scanner'
at Object.mkdirSync (fs.js:987:3)
at mkdirpManualSync (/home/jenkins/workspace/**********/**********/node_modules/sonarqube-scanner/node_modules/mkdirp/lib/mkdirp-manual.js:48:10)
at mkdirpNativeSync (/home/jenkins/workspace/**********/**********/node_modules/sonarqube-scanner/node_modules/mkdirp/lib/mkdirp-native.js:33:14)
at mkdirpSync (/home/jenkins/workspace/**********/**********/node_modules/sonarqube-scanner/node_modules/mkdirp/index.js:21:7)
at getSonarScannerExecutable (/home/jenkins/workspace/**********/**********/node_modules/sonarqube-scanner/dist/sonar-scanner-executable.js:98:3)
at scanCLI (/home/jenkins/workspace/**********/**********/node_modules/sonarqube-scanner/dist/index.js:31:3)
at Object.<anonymous> (/home/jenkins/workspace/**********/**********/node_modules/sonarqube-scanner/dist/bin/sonar-scanner:9:1)
at Module._compile (internal/modules/cjs/loader.js:1063:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1092:10)
at Module.load (internal/modules/cjs/loader.js:928:32) {
errno: -17,
syscall: 'mkdir',
code: 'EEXIST',
path: '/home/jenkins/.sonar/native-sonar-scanner'
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the **********@ sonar-scan script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
Is there something wrong with what we are doing? Is there a way to fix this?
The text was updated successfully, but these errors were encountered:
Hi,
We are seeing intermittent failures while running sonar scan on our Jenkins (UNIX) machines.
Before kicking off the scan, we run these custom commands
And we kickoff the scan via npm action defined in the package.json.
While running the above command, the sonar scanner is failing occasionally with the following error.
Is there something wrong with what we are doing? Is there a way to fix this?
The text was updated successfully, but these errors were encountered: