NPM Sonar Scanner fails to run on Jenkins CI (UNIX)

SonarQube Server / Community Build
,
1

Hi,

We are seeing intermittent failures while running sonar scan on our Jenkins (UNIX) machines.

We are using this npm package to run the sonar scan.

Version details:

  • sonarqube-scanner - 2.8.0

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?

2

Hi,

Welcome to the community!

You shouldn’t need to manually create the .sonar directory; the scanner handles that itself. Can you share why you started doing that?

 
Ann

3

Hi Ann,

Thanks for responding to the question. The custom script was something added by devops team. My understanding behind adding that script is to cache the sonar scanner executable and not download during every run, as nodes may start with clean state every run. Is that not required? Do you recommend removing the entire script?

Regards.

4

Hi,

Yes, I would remove that script.

 
Ann

5

Thanks. Will try that. I’ll share the update.

6

Removing that custom script worked so far. thanks for the help…

1 Like
7

Hi @ganncamp , I am noticing the issue even after removing that custom script.

Here’s the latest failure…

[06:21:51] Starting analysis...
[06:21:51] Checking if executable exists: /home/jenkins/.sonar/native-sonar-scanner/sonar-scanner-4.5.0.2216-linux/bin/sonar-scanner
[06:21:51] Could not find executable in "/home/jenkins/.sonar/native-sonar-scanner".
[06:21:51] Proceed with download of the platform binaries for SonarScanner...
[06:21:51] Creating /home/jenkins/.sonar/native-sonar-scanner
/home/jenkins/workspace/*****/dev/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/*****/dev/node_modules/sonarqube-scanner/node_modules/mkdirp/lib/mkdirp-manual.js:48:10)
    at mkdirpNativeSync (/home/jenkins/workspace/*****/dev/node_modules/sonarqube-scanner/node_modules/mkdirp/lib/mkdirp-native.js:33:14)
    at mkdirpSync (/home/jenkins/workspace/*****/dev/node_modules/sonarqube-scanner/node_modules/mkdirp/index.js:21:7)
    at getSonarScannerExecutable (/home/jenkins/workspace/*****/dev/node_modules/sonarqube-scanner/dist/sonar-scanner-executable.js:98:3)
    at scanCLI (/home/jenkins/workspace/*****/dev/node_modules/sonarqube-scanner/dist/index.js:31:3)
    at Object.<anonymous> (/home/jenkins/workspace/*****/dev/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! *****@ sonar-scan: `bin/sonar/run-sonar-scan.js "--token=****" "--gitSHA=*****" "--pullRequestId=*****" "--baseBranch=master" "--sourceBranch=*****"`
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.

This is happening very randomly and kind of concerning as its making the build jobs unstable and unreliable.

I’m also wondering, if this is a recommended approach or if there are any more reliable ways to perform scan.

8

Hi,

The scanner should be taking care of its own creation & cleanup. I suspect a permissions problem. Can you clean your workspace and try again?

 
Ann