Not to synchronize issue from main branch to short-live branch

  • Versions
    SonarQube: Developer Edition- Version 8.7 (build 41497)
    Scanner: sonar-scanner-4.5.0.2216-jenkins

  • What are you trying to achieve
    I want to not to synchronize issue from main branch to short-live branch setting is “New Code with reference branch”

Detail : We want to focus only for real “New Code”. What I mean is that we want track issues only for related with modified or created files in short-live branch.

For example, File “a” already modified at branch “A” and merged to master. And then, I make new branch B, and file “b” is modified. When I analyze branch “B”, I want to see only issues that related to file “b”. But there are some issue about file “a” with comment that “The issue has been copied from branch master to branch B”. I just focus on issue about file b, that created or modified in branch “B”.
Is there some option for this??

Here is my jenkins pipeline

${SONAR_SCANNER_HOME}/bin/sonar-scanner \
-Dsonar.projectKey=${SONAR_PROJECT_KEY} \
-Dsonar.branch.target=master \
-Dsonar.branch.name=${env.BRANCH_NAME} \
-Dsonar.scm.forceReloadAll=true \
-Dsonar.projectVersion=${SONAR_ANALYSIS_VERSION} \
-Dsonar.sources=. \
-Dsonar.inclusions=**/src/main/** \
-Dsonar.tests=. \
-Dsonar.test.inclusions=**/src/test/** \
-Dsonar.junit.reportPaths=build/test-results/test \
-Dsonar.coverage.jacoco.xmlReportPaths=**/target/site/jacoco/jacoco.xml \

Hey there.

Hi,

Your version is past EOL. You should upgrade to either the latest version or the current LTS at your earliest convenience. Your upgrade path is:

8.7 → 8.9.8 → 9.5 (last step optional)

You may find the Upgrade Guide and the LTS-to-LTS Upgrade Notes helpful. If you have questions about upgrading, feel free to open a new thread for that here.

If your issue persists after upgrade, please come back to us.