How to test config changes?

Template for a good new topic, formatted with Markdown:

  • ALM used (GitHub, Bitbucket Cloud, Azure DevOps)
  • CI system used (Bitbucket Cloud, Azure DevOps, Travis CI, Circle CI
    N/A - via CLI
  • Scanner command used when applicable (private details masked)
    ./gradlew sonar -Dsonar.token=**** -Dsonar.coverage.exclusions=“**/folder-to-exclude/*”
  • Languages of the repository
    Typescript, Java
  • Only if the SonarCloud project is public, the URL
    • And if you need help with pull request decoration, then the URL to the PR too
  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
    The branch in sonarcloud does not show any difference in coverage under overall code
  • Steps to reproduce
    build gradle project to get coverage report
    run above gradle sonar command
    Go look at the branch in sonarcloud
  • Potential workaround
    Do not share screenshots of logs – share the text itself (bonus points for being well-formatted)!

I figure I am doing something wrong here. I would expect my branch in sonar to have updated coverage information, but its exactly the same, and reporting on source files included in the sonar.coverage.exclusion parameter.


Welcome to the community!

Why would you expect that? Are you saying you’ve added coverage in the branch?

This is a different question, and we try to keep it to one topic per thread. Otherwise it can get messy, fast.

A quick take on this is to may try removing the quotes around the parameter value.