Different compilations of master branch causes scan graph teeth

[romanb52]

• Sonar Enterprise Edition Version 10.2 (build 77647)

We are using different azure devops pipelines to build parts of our application. First type of build is .NET code, then another pipeline compiles frontend - typescript, for example.
But probably because of the fact that every compilation contains quite different number of issues we see teeth in history graph of issues. Is it possible to somehow instruct sonar to combine more builds into one representation of data-graph?
For example all builds in one day? Or any other way?

Thanks,

Roman

[ganncamp (G Ann Campbell)]

Hi Roman,

I suspect this might be related to this:

Issue keeps on switching between statuses without any relevant changes

Hi @Carsten_HB, Thanks for reaching out and for the information that you provided! We’re already aware of an issue that might be related. Unfortunately, it’s not very easy to reproduce, so the investigation might take a while. In the meantime, feel free to share any other information or updates from your side that you think it might be relevant.

I was going to ask you to check the changelog of a few issues for repeated toggles between Open and Closed, but… it looks like that might have been factored out of the UI (hopefully accidentally).

Anyway… Since there’s not much you can check on your end, I’m going to pass this straight on to the team.

 
Ann

[ganncamp (G Ann Campbell)]

Hi again,

It’s just been pointed out to me that I’m both blind and forgetful. The Issue change log got moved into the tabs:

So could you double-check a few issues, please before I send this to the team?

 
Thx,
Ann

[romanb52]

Hello,

double checked

If you need more information let me know.

Thanks a lot,

Roman

[ganncamp (G Ann Campbell)]

Hi Roman,

Thanks for checking. We’ve got a ticket for this, but we’re still in the dark on the underlying cause, so I’ve flagged this for the team in case they have questions for you.

 
Thx,
Ann

[ganncamp (G Ann Campbell)]

Hi again,

My attention has just been called to this:

@romanb52

We are using different azure devops pipelines to build parts of our application. First type of build is .NET code, then another pipeline compiles frontend - typescript, for example.

When I read this, it didn’t occur to me that you might be analyzing two different sets of code with the same sonar.projectKey value…?

 
Ann

[romanb52]

Well yes. We have one git repository and under it (for simplicity) imagine having directories

• backend
• frontend

backend can be in C# or Java and frontend is for example react.

And we have different pipeline for backend build and frontend build.

I believe it is then a problem?

[ganncamp (G Ann Campbell)]

Hi,

Thanks. Yes, that’s the problem.

Analyses are not additive. Each new one naturally and fully replaces the previous one. So you need to analyze both your ends together () or as two separate projects.

 
Ann