No code change, but branch changed

SonarQube Cloud
1

Hello,

I know that I run an analyss twice on the same code, Sonar will complain there are no changes in the code.

But if I change of branch, and that this branch switch doesn’t lead to changes in the code, is Sonar supposed to complain, or is it supposed to do the analysis on this second branch ?

Scenario:

  1. I run an analysis on branch A
  2. I create a branch B from A
  3. I run an analysis on branch B
  4. I add some commits on A
  5. I run an analysis on branch A
  6. I rebase B on A
  7. I run an analysis on branch B
2

Hi @Oodini,

Could you clarify your post a bit further?

  • When you mention Sonar is “complaining,” can you explain what specific warnings or errors you are seeing?
  • What behavior is actually happening, and how does that differ from what you expect to happen?

Screenshots are super helpful, or an open source repo that reproduces the behavior on a public SonarQube Cloud project.

3

I have no problem right now, actually. I am touching my Jenkins script.

For the “complain”, I am referring to the message in the log telling the JSON is empty because no code has changed.

4

Can you share the message?