ESLint reports import into SonarQube Cloud stopped

SonarQube Cloud
1
  • ALM used: GitHub
  • CI system used: Jenkins
  • Scanner command used: mvn -Duser.home= org.sonarsource.scanner.maven:sonar-maven-plugin:sonar --batch-mode -pl -pl --also-make --no-snapshot-updates -Psonar -Dsonar -Dsonar.projectName= -Dsonar.projectKey= -Dsonar.organization= -Dsonar.host.url=https://sonarcloud.io -Dsonar.token= -Dsonar.branch.name=develop -Dmaven.repo.local= -f /Parent/pom.xml
  • Languages of the repository: Java, TS, JS

Since 22 September we face a problem: ESLint issues have not been imported into SonarQube Cloud:

  • the ESLint reports are physically still present on their usual locations
  • Maven pom.xml still has sonar.eslint.reportPathswith proper data

In our CI log we don’t have now these lines Importing external issues from which in the past were indicator SonarQube Cloud truly imports the reports.

Hence we have a lot of ESLint issues falsely closed in SonarQube Cloud.

4

Hello @lrozenblyum,

can you share the full debug logs of the analysis, please?

Thanks!

7

is -Dsonar.verbose passing to Maven enough of we should use -X instead?

8

-X is enough

9

Sent in private

10

Looks to be fixed by the SonarCloud team. Thanks for the speed!

1 Like