All, We've been tweaking around with SonarCloud over the past few days to try and understand why our JS was no more analyzed VS what we had in SonarQube, Looking at SonarCloud ONAP projects, none were reporting JS https://sonarcloud.io/organizations/onap/projects, so we suspected that there was something different. It seems that the SonarCloud Analyzer requires to have access to the executable of node.js on the build node to allow for the analysis to be run, not sure if this was the case before (apparently new since SQ 7.8). We have fixed it by pointing sonar to our own instance of node.js that we provide in our build (this way, we control the node.js version that we want).
You can take a look at the CLAMP pom.xml<https://gerrit.onap.org/r/gitweb?p=clamp.git;a=blob;f=pom.xml> file if you want to see how we've enabled it, also excluding test.js sources to properly report coverage. Hope it helps Regards Christophe -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#19848): https://lists.onap.org/g/onap-discuss/message/19848 Mute This Topic: https://lists.onap.org/mt/70218540/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
