How to avoid WARNING 'Missing blame information for the following files'

SonarCloud
1
  • ALM used - GitHub
  • CI system used - wercker
  • Scanner command used when applicable (private details masked)
    …
  • Languages of the repository - java
  • Only if the SonarCloud project is public, the URL - https://sonarcloud.io/dashboard?id=org.checkstyle%3Acheckstyle
  • And if you need help with pull request decoration, then the URL to the PR too - Not applicable
  • Error observed (wrap logs/code around with triple quotes ``` for proper formatting)
[INFO] SCM Publisher SCM provider for this project is: git
[INFO] SCM Publisher 530 source files to be analyzed
[WARNING] Shallow clone detected, no blame information will be provided. You can convert to non-shallow with 'git fetch --unshallow'.
[INFO] SCM Publisher 0/530 source files have been analyzed (done) | time=4ms
[WARNING] Missing blame information for the following files:

  • Steps to reproduce
    execute validation in CI

  • Potential workaround

no workaround as CI is not configurable to provide git clone with history

How to disable this warning ? it is limitation of CI, it pollutes logs a lot and we do not need blame at all, failed gate is problem of whole team, not a certain person.

2

Hi @romani,

It is currently not possible to disable this warning and we currently do not have any plans to include this feature. Please post this suggestion to Suggest New Features.

Not having the full git history available when scanning will break quite some features like PR analysis and automatic assignment of issues to the creator of those issues, so we want to be sure that users are aware of this limitation.

3

I’m using GitLab CI and GIT_DEPTH: "0" (https://docs.sonarqube.org/latest/analysis/gitlab-cicd/) env var helped me. It’s related to shallow clone feature