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

A CE task should not be associated to a module

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 6.7
    • Component/s: Compute Engine
    • Labels:

      Description

      To reproduce:

      1. Analyse a Maven project with key "my-company:main" and a submodule with key "my-company:foo"
        • Execution of analysis is successful
        • You can browse the project at the URL provided by the logs =>
      2. Analyse the sub-module "my-company:foo" directly in its folder
        • Execution of analysis is successful
        • You can browse the project module at the URL provided by the logs =>
          • You see a "Failed" badge on the top right corner - which is not expected
          • You can access the "Background Tasks" page for that module - which is not expected (see SONAR-8966)
          • You can even see on this "Background Tasks" page that the module actually has a task that failed (with a proper message fortunately) - which is not expected

      From an end-user point of view, all this is misleading (even though, to some extend, it's helpful to understand what happened).

      One option to prevent this misleading situation would be to fail fast on Scanner side when we detect that someone tries to analyze a project that is an existing module.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                julien.lancelot Julien Lancelot
                Reporter:
                fabrice.bellingard Fabrice Bellingard
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: