Affects Version/s: None
Fix Version/s: None
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.
- 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.
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.