Nsryjdtyk

I am using SonarQube 5.6.1 for code analysis (code written in Spring Boot and Angular (using TypeScript)). SonarQube Scanner for Maven 3.4.0.905 and SonarTsPlugin 1.1.0 are used for code scanning in Java and TypeScript, respectively.

In my pom.xml, I have the following properties set:

<frontend.directory>frontend</frontend.directory>

<sonar.host.url>http://sonarqube.some-url.local/</sonar.host.url>

<sonar.sources>src/main/java,${frontend.directory}/src/app,pom.xml</sonar.sources>

<sonar.exclusions>${frontend.directory}/node_modules/**</sonar.exclusions>

<sonar.tests>${frontend.directory}/src/app,src/test/java</sonar.tests>

<sonar.test.inclusions>**/*.spec.ts,src/test/java/**/*.java</sonar.test.inclusions>

<sonar.testExecutionReportPaths>${frontend.directory}/reports/ut_report.xml</sonar.testExecutionReportPaths>

<sonar.ts.coverage.lcovReportPath>${frontend.directory}/coverage/lcov.info</sonar.ts.coverage.lcovReportPath>

<sonar.ts.tslint.configPath>${frontend.directory}/tslint.json</sonar.ts.tslint.configPath>

<sonar.ts.tslint.nodePath>${frontend.directory}/node/node</sonar.ts.tslint.nodepath>

<sonar.ts.tslint.path>${frontend.directory}/node_modules/.bin/tslint</sonar.ts.tslint.path>

Please note that I am pointing sonar.ts.tslint.nodePath to the local node installed as following.

I use frontend-maven-plugin 1.6 to install npm and node:

<plugin>

    <groupId>com.github.eirslett</groupId>

    <artifactId>frontend-maven-plugin</artifactId>

    <version>1.6</version>



    <configuration>

        <workingDirectory>${frontend.directory}</workingDirectory>

    </configuration>



    <executions>

        <execution>

        <id>install node and npm</id>

        <goals>

            <goal>install-node-and-npm</goal>

        </goals>

        <configuration>

            <nodeVersion>v10.1.0</nodeVersion>

            <npmVersion>6.0.1</npmVersion>

        </configuration>

        </execution>

        ...

    </executions>

</plugin>

I run ./mvnw sonar:sonar to start the SonarQube scanner. However, when the SonarTsPlugin runs and goes to run tslint, the nodePath is ignored and the global node is used. This causes problems in my Jenkins box where I get the following error:

[ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:3.4.0.905:sonar (default-cli) on project nsgra-web: java.io.IOException: Cannot run program "node": error=2, No such file or directory -> [Help 1]

This is odd to me since node is installed via frontend-maven-plugin and I am pointing to that node binary in sonar.ts.tslint.nodePath.

Does anyone have any insight?

Thanks Aerus for your response.

I found the same issue inside docker pod using jenkins.

I had maven installed but not node, then maven create a local installation of node at ./node/ folder. When the TS sonar was trying to execute node to know the current version, the commented error arise and all .ts files was ignored.

I solved using your suggestion and adding this to the command line execution

-Dsonar.typescript.node=./node/node