Tag: sonarqube
运行sonarqube分析我的代码时得到NullPointerException
我有一个Jenkins的工作来发布unit testing覆盖（lcov格式）到SonarQube服务器，如问题及其答案中所述。 有时，我在Jenkins控制台日志的node_modules目录中看到以下JavaScript文件exception。 16:57:15.037 ERROR – Problem while calculating coverage for /var/lib/jenkins/jobs/jenkins-project-name/workspace/project-name/node_modules/js-tokens/test/fixtures/regex.js java.lang.NullPointerException: null at org.sonar.plugins.javascript.lcov.UTCoverageSensor.saveZeroValueForResource(UTCoverageSensor.java:146) [sonar-javascript-plugin-2.9.jar:na] at org.sonar.plugins.javascript.lcov.UTCoverageSensor.saveMeasureFromLCOVFile(UTCoverageSensor.java:128) [sonar-javascript-plugin-2.9.jar:na] at org.sonar.plugins.javascript.lcov.UTCoverageSensor.analyse(UTCoverageSensor.java:85) [sonar-javascript-plugin-2.9.jar:na] at org.sonar.batch.phases.SensorsExecutor.executeSensor(SensorsExecutor.java:58) [sonar-batch-shaded-5.2.jar:na] at org.sonar.batch.phases.SensorsExecutor.execute(SensorsExecutor.java:50) [sonar-batch-shaded-5.2.jar:na] at org.sonar.batch.phases.PhaseExecutor.execute(PhaseExecutor.java:98) [sonar-batch-shaded-5.2.jar:na] at org.sonar.batch.scan.ModuleScanContainer.doAfterStart(ModuleScanContainer.java:192) [sonar-batch-shaded-5.2.jar:na] at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:100) [sonar-batch-shaded-5.2.jar:na] at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:85) [sonar-batch-shaded-5.2.jar:na] at org.sonar.batch.scan.ProjectScanContainer.scan(ProjectScanContainer.java:258) [sonar-batch-shaded-5.2.jar:na] at org.sonar.batch.scan.ProjectScanContainer.scanRecursively(ProjectScanContainer.java:253) [sonar-batch-shaded-5.2.jar:na] at org.sonar.batch.scan.ProjectScanContainer.doAfterStart(ProjectScanContainer.java:243) [sonar-batch-shaded-5.2.jar:na] at org.sonar.core.platform.ComponentContainer.startComponents(ComponentContainer.java:100) [sonar-batch-shaded-5.2.jar:na] at org.sonar.core.platform.ComponentContainer.execute(ComponentContainer.java:85) […]
伊斯坦布尔和声纳之间的分支覆盖率不匹配
我的Jenkins工作通过Sonar Runner读取由伊斯坦布尔生成的lcov文件。 伊斯坦布尔生成的lcov报告中的数字/未命中与Sonar中显示的不匹配。 与伊斯坦布尔相比，有0-7％的差距因寻找更多的失误而变得更加严格。 是否预计？ 为什么区别？ 环境： SonarQube 3.5和3.7.4 SonarRunner 2.3 Sonar JavaScript插件1.6 Node.js代码
用grunt-karma-sonar进行unit testing
我正在尝试使用Grunt，Karma和Sonar进行unit testing和testing覆盖。 我正在通过这个教程 。 这是我的依赖： "devDependencies": { "bower": "~1.3.1", "grunt": "~0.4.4", "grunt-autoprefixer": "~2.0.0", "grunt-cli": "~0.1.13", "grunt-contrib-jasmine": "~0.6.1", "grunt-karma": "~0.8.0", "grunt-karma-sonar": "~0.1.3", "istanbul": "~0.4.2", "jasmine-core": "~2.3.4", "karma": "~0.12.0", "karma-chrome-launcher": "~0.1.12", "karma-coverage": "~0.2.0", "karma-firefox-launcher": "~0.1.6", "karma-jasmine": "~0.2.1", "karma-junit-reporter": "~0.2.1", "karma-phantomjs-launcher": "~0.1.2", "karma-junit-sonarqube-reporter": "0.0.1", "load-grunt-tasks": "^3.4.0", "phantomjs": "~1.9.19", } 这是我的gruntfile： //require('load-grunt-tasks')(grunt); module.exports = function (grunt) { var $srcFiles […]
