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

Introduce "What if" capability on server-side

    XMLWordPrintable

    Details

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

      Description

      The purpose of this "what if" concept is to cover the following use cases:

      • I'm running preview analyses on my pull requests and I want to know what would be the status of the quality gate if the code would be merged into the main code base
      • I have pre-commit hooks in my SCM that should prevent code which might break the quality gate to be checked-in
      • I don't have pre-commit hooks nor pull requests analyses for my project, but still I want to make sure that if I push my code, it won't break the quality gate

      All the use cases have in common the following points:

      • I want to know what the quality gate would be if I would push the code into the main code base
      • , but at the same time, I don't want the analysis history of my project on the SonarQube server to be "polluted" by such information

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              julien.henry Julien Henry
              Votes:
              47 Vote for this issue
              Watchers:
              53 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: