PR decoration/ GitHub checks is placed on main instead of PR

SonarQube Cloud
1

Hello,

after applying this workaround for forked PRs, the check results are attached to the current main branch instead of the PR that actually triggerd the analysis. However, the sonarcloud bot is finding the correct branch to comment the test result.

Is there a way to configure this to refer back to the triggering PR?

We’re using:

mvn -B verify -P coverage sonar:sonar 
-Dsonar.projectKey=FraunhoferIOSB_FAAAST-Package-Explorer-Converter 
-Dsonar.pullrequest.key='${{ steps.fetch.outputs.pr-number }}' 
-Dsonar.pullrequest.branch='${{ github.event.workflow_run.head_branch }}' 
-Dmaven.javadoc.skip=true
  • Project properties from the background task
Project scanner properties:
  - sonar.binaries=/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter/target/classes
  - sonar.dynamicAnalysis=reuseReports
  - sonar.groovy.binaries=/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter/target/classes
  - sonar.host.url=https://sonarcloud.io
  - sonar.java.binaries=/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter/target/classes
  - sonar.java.coveragePlugin=jacoco
  - sonar.java.jdkHome=/usr/lib/jvm/temurin-11-jdk-amd64
  - sonar.java.libraries=/home/runner/.m2/repository/ch/qos/logback/logback-classic/1.2.11/logback-classic-1.2.11.jar,/home/runner/.m2/repository/ch/qos/logback/logback-core/1.2.11/logback-core-1.2.11.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.13.3/jackson-core-2.13.3.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.13.3/jackson-databind-2.13.3.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-annotations/2.13.3/jackson-annotations-2.13.3.jar,/home/runner/.m2/repository/com/jayway/jsonpath/json-path/2.7.0/json-path-2.7.0.jar,/home/runner/.m2/repository/net/minidev/json-smart/2.4.7/json-smart-2.4.7.jar,/home/runner/.m2/repository/net/minidev/accessors-smart/2.4.7/accessors-smart-2.4.7.jar,/home/runner/.m2/repository/org/ow2/asm/asm/9.1/asm-9.1.jar,/home/runner/.m2/repository/info/picocli/picocli/4.6.3/picocli-4.6.3.jar,/home/runner/.m2/repository/io/admin-shell/aas/dataformat-core/1.2.1/dataformat-core-1.2.1.jar,/home/runner/.m2/rep...
  - sonar.java.source=1.8
  - sonar.java.target=1.8
  - sonar.java.test.libraries=/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter/target/classes,/home/runner/.m2/repository/ch/qos/logback/logback-classic/1.2.11/logback-classic-1.2.11.jar,/home/runner/.m2/repository/ch/qos/logback/logback-core/1.2.11/logback-core-1.2.11.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.13.3/jackson-core-2.13.3.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.13.3/jackson-databind-2.13.3.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-annotations/2.13.3/jackson-annotations-2.13.3.jar,/home/runner/.m2/repository/com/jayway/jsonpath/json-path/2.7.0/json-path-2.7.0.jar,/home/runner/.m2/repository/net/minidev/json-smart/2.4.7/json-smart-2.4.7.jar,/home/runner/.m2/repository/net/minidev/accessors-smart/2.4.7/accessors-smart-2.4.7.jar,/home/runner/.m2/repository/org/ow2/asm/asm/9.1/asm-9.1.jar,/home/runner/.m2/repository/info/picocli/picocli/4.6.3/picocli-4.6.3.jar,/home/runner/....
  - sonar.language=java
  - sonar.libraries=/home/runner/.m2/repository/ch/qos/logback/logback-classic/1.2.11/logback-classic-1.2.11.jar,/home/runner/.m2/repository/ch/qos/logback/logback-core/1.2.11/logback-core-1.2.11.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-core/2.13.3/jackson-core-2.13.3.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-databind/2.13.3/jackson-databind-2.13.3.jar,/home/runner/.m2/repository/com/fasterxml/jackson/core/jackson-annotations/2.13.3/jackson-annotations-2.13.3.jar,/home/runner/.m2/repository/com/jayway/jsonpath/json-path/2.7.0/json-path-2.7.0.jar,/home/runner/.m2/repository/net/minidev/json-smart/2.4.7/json-smart-2.4.7.jar,/home/runner/.m2/repository/net/minidev/accessors-smart/2.4.7/accessors-smart-2.4.7.jar,/home/runner/.m2/repository/org/ow2/asm/asm/9.1/asm-9.1.jar,/home/runner/.m2/repository/info/picocli/picocli/4.6.3/picocli-4.6.3.jar,/home/runner/.m2/repository/io/admin-shell/aas/dataformat-core/1.2.1/dataformat-core-1.2.1.jar,/home/runner/.m2/rep...
  - sonar.links.ci=
  - sonar.links.homepage=https://github.com/FraunhoferIOSB/FAAAST-Package-Explorer-Converter
  - sonar.links.issue=https://github.com/FraunhoferIOSB/FAAAST-Package-Explorer-Converter/issues
  - sonar.links.scm=https://github.com/FraunhoferIOSB/FAAAST-Package-Explorer-Converter/tree/main
  - sonar.links.scm_dev=scm:git:ssh://github.com:FraunhoferIOSB/FAAAST-Package-Explorer-Converter.git
  - sonar.moduleKey=FraunhoferIOSB_FAAAST-Package-Explorer-Converter:de.fraunhofer.iosb.ilt.faaast:package-explorer-converter
  - sonar.organization=fraunhofer-iosb
  - sonar.projectBaseDir=/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter
  - sonar.projectBuildDir=/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter/target
  - sonar.projectDescription=Converter for AASX Package Explorer JSON files to be used with FA³ST
  - sonar.projectKey=FraunhoferIOSB_FAAAST-Package-Explorer-Converter
  - sonar.projectName=package-explorer-converter
  - sonar.projectVersion=0.3.0-SNAPSHOT
  - sonar.pullrequest.branch=pr-to-fail-Sonar-Quality-Gate
  - sonar.pullrequest.key=12
  - sonar.scanner.app=ScannerMaven
  - sonar.scanner.appVersion=3.9.1.2184/3.8.6
  - sonar.sourceEncoding=UTF-8
  - sonar.sources=/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter/pom.xml,/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter/src/main/java
  - sonar.working.directory=/home/runner/work/FAAAST-Package-Explorer-Converter/FAAAST-Package-Explorer-Converter/target/sonar

Cheers

3

Hi,

Could you provide your anlaysis logs?

Also I see that the action also shows up on PR #12 and that the results for main and PR #12 have different coverage percentages. How many times has PR #12 been analyzed?

 
Ann

9

Hi @ChrisWeiss,

We have checked the current status
The branch seems to have a commit which is the final one on the PR.
I was wondering do you still experiencing the issue?