Uploaded image for project: 'SonarQube Scanner for Jenkins'
  1. SonarQube Scanner for Jenkins
  2. SONARJNKNS-316

Pipelines with multiple analysis steps are not correctly supported

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Pipeline
    • Labels:
      None

      Description

      Why

      A Jenkins pipeline can be declared with multiple analysis steps, for instance on mono-repositories. In this context a few unexpected behaviors should be improved:

      • The Jenkins widget shows only the results of the first executed analysis. Others are ignored.
      • The step waitForQualityGate is associated with the last executed analysis only. It does not wait for other analyses.

      These limitations are not restricted to parallel analyses. They exist on sequential analyses too.

      What

      • The Jenkins widget should mimic the behavior of the Bitbucket Pipeline widget by displaying as many sections as analyses.
      • The step waitForQualityGate should wait for the results of all the analyses steps declared before it. It's still up to users to correctly declare waitForQualityGate after analyses.

      How

      The context parameter used for the inter-communication between analysis steps and waitForQualityGate step should be a list of analysis IDs, but not a single ID.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              simon.brandhof Simon Brandhof (Inactive)
              Votes:
              7 Vote for this issue
              Watchers:
              12 Start watching this issue

                Dates

                Created:
                Updated: