Branch plugin not analysising new code

SonarQube version - 7.9.1 (build 27448)
SonarScanner version - “4.2.0.1873”

Coverage report changes when using branches.
Javascript project, working with Jest. Here’s the layout:

When creating the master branch without the -Dsonar.branch.name argument, the master branch picks up the coverage. When checking out to a feature branch, making a change within the src/ directory is seems that the coverage doesn’t change and am unable to see the Code changes within the “Code” window in the UI. I have checked locally within the coverage report and it’s noticed, just seems that it isn’t being analyzed on a branch.

Here’s the sonar-scanner.properties file:

sonar.language=js
sonar.profile=node

sonar.projectVersion=1.0
sonar.sourceEncoding=UTF-8

sonar.sources=src
sonar.exclusions=deploy/**
sonar.inclusions=server.js

# Tests
sonar.tests=test
sonar.test.inclusions=**/*.test.js

# Coverage
sonar.coverage.exclusions=sub-system-tests/**,**/*.py,**/*.json,**/*.xml
sonar.javascript.coveragePlugin=lcov
sonar.javascript.lcov.reportPaths=coverage/lcov.info

Hey there.

How are you running analysis? Locally or with a CI tool? Have you committed the changed files before. running analysis? This is required for the detection of changed files/lines to occur.

Also, a heads up that these parameters aren’t doing anything anymore. You can clean them up! :smiley: