SonarQube reference code for “New code”

Orekit development
1

Dear all,

During a conversation with @MaximeJ, I reviewed the configuration of the Orekit project in SonarQube. One detail in the reference version of the code bothers me:

  • main: new code is evaluated against the previous version

  • develop: new code is evaluated against the main branch

  • Other branches: new code is evaluated against the main branch

It seems to me that it would make more sense to evaluate the new code in the other branches against the develop branch (except for the release-X.Y branches, which should indeed be evaluated against the main branch or the previous release-X.Y, which must be set manually each time). What do you think?

Best regards

3 Likes
2

I agree with you.

3

Hi,

I think the other branches in general should be compared to develop and not main, as we systematically create them from develop. With the exception of the release-X.Y branches as you already mentioned.

Regards

4

Since no one raised any objections and everyone who spoke was in favor of this change, I have just made it.

1 Like