Outdated Pull Request decorations in GitHub

SonarQube Cloud
1

Hi, community.
It seems that PR decorations sent to GitHub look a bit outdated.
I have set up manual analysis using AWS CodeBuild, just like it was suggested during project creation.

When I tested automatic analysis, PR decorations looked more “fresh”.

Any clues why it might be happening?

Thanks

Attached screenshot how it looks now.

Edit: sonar-scanner version - 5.0.1.3006

  • ALM used - GitHub
  • CI system used - AWS CodeBuild
  • Languages of the repository - JavaScript, TypeScript
  • Scanner command:
        sonar-scanner \
            -Dsonar.organization=${sonar_organization} \
            -Dsonar.projectKey=${sonar_project_key} \
            -Dsonar.host.url=https://sonarcloud.io \
            -Dsonar.exclusions=**/*.html,**/*.css,**/*.scss,**/*.yaml,**/*.json,**/*.config.* \
            -Dsonar.test.inclusions=**/*.spec.ts \
            -Dsonar.pullrequest.key=$${PULL_NUM} \
            -Dsonar.pullrequest.branch=$${HEAD_REF} \
            -Dsonar.pullrequest.base=$${BASE_REF} \
            -Dsonar.pullrequest.provider=GitHub \
            -Dsonar.pullrequest.github.repository=${github_org_name}/${repository_name} \
            -Dsonar.qualitygate.wait=true \
            -Dsonar.javascript.lcov.reportPaths=coverage/lcov.info \
            -Dsonar.testExecutionReportPaths=coverage/test-report.xml

image
image962×554 42.5 KB

2

Hey there.

I think you might be referring to the same change as this user. Am I correct?

3

Yeah, precisely, was looking for that aesthetic feedback.

Thanks for letting me know!