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

Log scanner context when processing Compute Engine task

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 5.2
    • Component/s: Compute Engine, Scanner
    • Labels:
      None

      Description

      The idea is to include the following information in the report sent by the batch:

      • all the properties used for the analysis (equivalent of what is dumped on batch side when we want to debug)
      • all the JVM properties (that will give info about the OS, the processor, ...)
      • plugins that are used for the analysis and their version
      • the SonarQube user that performs the analysis (maybe it is already given by the JVM property "java.user")
      • the targeted SonarQube server (url, serverID)

      Notes:

      • We should be very cautious with sensitive data, like properties that might have been encrypted and that we would not want to include in this file. For this matter:
        • environment variables and JVM properties should be dumped only when the analysis is run with the "sonar.verbose=true" command
        • the properties used for the analysis should be based on a white list that includes "sonar*" properties
      • It would be useful that this file is kept in the work folder of the batch analysis, so that ops can use it to debug why a batch analysis failed.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                fabrice.bellingard Fabrice Bellingard
                Reporter:
                fabrice.bellingard Fabrice Bellingard
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: