Sonarcloud generate coverage folder in master

Hello. There are no errors in the pull requests, but after the merge, a large number of bugs appear and the code smells from the automatically generated coverage folder with files like:

  • ALM used - Bitbucket Cloud
  • CI system used - Bitbucket Cloud

Please share instructions on how to disable the generation of this folder?

Hi @a5okol , welcome to the community.

Not sure how exactly this is being generated (probably that you have some test with coverage running as part of your build process)

This can be however easily excludable by setting sonar.exclusions=coverage/*