Desync Between Sonar Portfolio Overview and Projects

SonarQube Cloud
, ,
1

Hi everyone,

We are using both the Portfolio Overview and the Project Overview within SonarCloud Enterprise. Here we have noticed that the measures do not align with the actual underlying projects. The integration we are using is done with Azure DevOps Services.

For example: The portfolio displays a LoC count of 48,5k (overall), while the project itself displays 46,6k (overall on main). We have a couple (not all) projects where this is the case.

The same occurs for the code coverage, i.e. the portfolio displays the overall coverage for one of our projects at ~55%, while the project overview shows overall 75% (on main). Generally the difference for our coverage results is the biggest, which are quite far apart from each other.

I cannot explain the behavior on why this happens. I can share further details on our project setup within a private conversation.

Regards

Shawn Funke

Sonar Community Roundup, December 5 - 12
4

Hey @shfunke!

Can you share some screenshots of the discrepancies you’re seeing? I can’t reproduce this on any of our internal portfolios. It would be good to see exactly where you’re seeing the discrepancy.

7

Hi @shfunke!

A few clarifying questions:

  1. Have any of the portfolio definitions changed recently, or did you delete any projects that were in this portfolio? (Asking because we recently found some buggy behavior in that space.)

  2. Are these individual, siloed git projects, or are some of them grouped together in a monorepo?

8

Hi Christoph,

  1. No I did not change anything - there is a wildcard inclusion for the projects that are of relevance. That’s it.
  2. It is a mixed of both, where the problem shows up for “normal” projects and mono-repo projects.
9

Hi Colin, I can share screenshots in a private conversation regarding the project in question.

Would that be possible?

10

Hi @shfunke,

If you remove any project from the portfolio and then re-add it, it should cause the portfolio to be recomputed. Could you try that to see if it somehow fixes these weird discrepancies?

Also, I’ll send you a private message that you can reply to with any screenshots you think might be helpful.

11

Hi Cody,

We have a Portfolio, and import projects via a regular expression, similar to: “something_example_.*”.

I have removed the filter (deleting all projects from them) and set the filter again, thus reimported them. This resulted in the overview showing the correct numbers and measures.

So I assume that this is an issue with the portfolio not updating when a regular expression is used to select the projects.

Regards

Shawn Funke

12

Hi @shfunke,

Thanks so much, that is super helpful information. I’ll continue to investigate from there.

1 Like
13

Hi Cody , were you able to reproduce the issue?

The easiest way for me was to create a new project, have it being included in the portfolio and upload results for the projects.

Is there a recommended workaround that I should apply in the meantime that you can recommend?

14

Hi @shfunke,

Really sorry for the delayed response.

I was not to reproduce the issue, but we are aware of some strange behavior with portfolios and have it in our backlog to investigate further.

Unfortunately, I don’t have a suggestion that is better than your current workaround.

15

Hi, I discovered a bug today that prevents portfolios with dynamic project selection (regex in this case) from being recalculated when matching projects are reanalyzed.

This is likely the same issue. We will do our best to fix this bug next iteration!

1 Like
22

Hi Daniel, that is great to hear!

Will you provide an update here when you have pushed the fix?

23

Hi,

The fix has already been deployed. The portfolio should update the next time the project is analyzed.

 
Ann

24

Alright, great! I’ll consider this closed and only report back if I find any other issue related to this.

Thank you very much for the help!

1 Like