SonarCloud Pull Request integration with multiple builds

[bill.benjamin]

+1 This is a huge pain for us, as well. We can work around the issue by triggering the Pull Request Builds manually, one at a time, but this really defeats the ease of use and we are dependent on developers following this process to prevent new issues getting into our codebase

[Alex_Denton]

+1 Throwing my hat in the ring here. I very much want this feature as well.

[Alex_Denton]

@Fabrice_Bellingard I don’t see anything on your product roadmap for this functionality. I wonder if you could give us a better sense of the timeline? Is this something you’d like to get does this quarter? This year? Next year? Not scheduled? Is it in the bottom of the pile or in the middle or unprioritized?

I understand these are difficult questions. If the honest answer is “don’t know” I can accept that but I will want to find my own work-arounds.

Thanks!

[Fabrice_Bellingard]

Hi Alex, Bill, Joao, Stephen and Greg,

Situation has not changed since my last post 3 weeks ago:

@Fabrice_Bellingard

Hi all, just to give you heads up on this: we were not able to progress on that topic just yet. This is not forgotten - just not on the top of the list of the current priorities.

Be sure that on my side, this issue is definitely in my radar. As you pointed out @Alex_Denton, this is quite tricky, especially given the the way scanners and analyses are currently designed. There is no obvious and quick solution which comes to mind, and this needs to be investigated in depth with team mates who know the Microsoft world very well (and they’re very busy those days…).

If I had to give an estimated timeframe when I feel we’ll be able to investigate this in depth, I’d say in about 2 months from now.

[Alex_Denton]

I appreciate that. It definitely helps with planning on my side. I’ll be greatly looking forward to this feature.

Thanks to and your team for your hard work!

[maxhov (Max)]

+1 would be very welcome feature.

[clakech (Cyril Lakech)]

We have the exact same issue here but with github:

GitHub pull request decorations for monorepos

Hello, We have a monorepo with 2 projects at the root of the repository: api webapp api use Maven/Java/sonar webapp use npm/typescript/sonar We setup pull request decorations using sonarcloud.io Circleci and GitHub Since we can have 2 separate analysis in the same pull-request containing change into api and webapp, how to have 2 distincts decoration in GitHub checks on the pull request, one for the api, another for the webapp?

So this issue is closed as duplicate, that’s why I come here to ask for this feature too.

Would be useful to be able to have distincts sonar PR decoration for each sonar analysis triggered by the build:
If I modified several modules in the same PR, then I will triggered distinct sonar analysis and I would like to have distinct PR decoration for each modified modules.

[StephenLarkin]

Hi @Fabrice_Bellingard, I’m sure I’m not the only one who has been waiting with bated breath to see how this was progressing. I was wondering if it was possible to get an update on the timeline for this feature?

[gregpakes]

You’re not the only one…

[gregpakes]

8 Months and counting…

[Fabrice_Bellingard]

@StephenLarkin

I was wondering if it was possible to get an update on the timeline for this feature?

We’ve recently onboarded a new member in our crew who is going to dedicate all his energy on the Azure DevOps user experience, and as soon as he’s up-to-speed, this topic is going to be the first tricky one on his list! (no pressure @mickaelcaro )

[DanS]

Also facing the same issue here.

We have a repo with multiple projects that are scanned differently.

I have configured a Jenkins job with multiple sonar scanners, however if an issue is found with the 1st project, the status is overwritten by the 2nd, 3rd and 4th scan.

A simple fix would be to give us the ability to assign the Status context name, e.g. sonar.pullrequest.statusname=Sonarqube-1

Could we please have an update regarding this issue?

[Fabrice_Bellingard]

@DanS Can you detail what type of project your are analyzing in this repository, using which scanner, please?

[cjancsar]

We have the exact same requirement. Monorepo but only one status gate shows in PR checks on Github. Where is this issue at?

[clakech (Cyril Lakech)]

we have a mono repo with several module inside: 1 java api, 1 front js, 1 front js, 1 batch, etc.

when we create a pull request we need to exec several sonar analysis: 1 java, 2 js, 1 other etc.

but only the latest analysis will be used by github pull request apps to display results.

we would like to have all results in differents checks as we can have with circleci builds steps for instance.

[StephenLarkin]

Hey @Fabrice_Bellingard and @mickaelcaro any chance of another update on where we are with this?

[mickaelcaro (Mickaël Caro)]

Hi,

We were busy looking at this, and here is some update :

It will be more complicated that we originally thought

Some use cases are working, and we are going to document them in the SonarCloud documentation.

But for other more complicated scenarios (like analyzing a same repository by multiple pipelines), we just realize that it will need deeper modifications in the engine.

Hope that you will understand, we be sure to let you know about newest updates !

Thank you for your understanding.

Mickaël

[dennisdoomen]

This is really a serious problem in any modern day full-stack repository. I’m surprised that this is still not solved, given how many companies break down their monoliths in full-stack services and components.

[StephenLarkin]

Hey @Fabrice_Bellingard and @mickaelcaro, it’s that time again that I bother you to see how things are progressing.

[StephenLarkin]

Hey, I know you guys are probably busy, but has there been any movement on this? @Fabrice_Bellingard @mickaelcaro?