Uploaded image for project: 'SonarQube'
  1. SonarQube
  2. SONAR-7412

Inconsistent last revision of file persisted in FILE_SOURCES

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 5.2, 5.3, 5.4
    • Fix Version/s: 5.6
    • Component/s: Compute Engine
    • Labels:

      Description

      Given a file commit and analyzed, if this file is modified, not commit in SCM and analyzed, the scanner does not send any SCM info about the file, therefor no line in FILE_SOURCES for this file have any SCM information.
      Still, the column FILE_SOURCES.REVISION is populated with the value of this column from the previous analysis.

      In such state, FILE_SOURCES content for this file is inconsistent: file has a latest revision but no line has any revision.

      Problem cause by this inconsistency:
      scanner consider server has Scm information and will not send any (unless file source hash has changed) and will not send any.

      This inconsistency can also be created when:

      • SCM is disabled (sonar.scm.disabled=true)
      • SCM provider has been uninstalled
      • ... (ie. any reason report does not contain the Scm information of the file)

      The inconsistency will fix itself when the file content is changed and the file commit and analyzed.

      In case of urgent need, one can also run an analysis with sonar.scm.forceReloadAll=true to force scanner to send SCM information for all files.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              sebastien.lesaint Sebastien Lesaint
              Reporter:
              sebastien.lesaint Sebastien Lesaint
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Due:
                Created:
                Updated:
                Resolved: