Get SonarCube tracking net code from latest release (unstable branch)

[aleksraiden]

Add a latest release branch as sonar.newCode.referenceBranch to track a new code, added after latest release. Closes #2058, #2059

[jihuayu]

I am testing this modification on my test project to see if it takes effect. This will take some time, please wait.

[jihuayu]

I have a try, but it doesn't work in my repo. Does it work in your repo? @aleksraiden

Following the doc, It seems like the sonar.newCode.referenceBranch option is only supported by SonarQube. In SonarCloud we don't have this option.

SonarCloud only version and Number of days.
Maybe we can use the Specific date option, and use the last 30 days' code as new code in sonarcloud setting. @git-hulk
This option can fixed #2059.

And the #2058 is another problem. I am trying it in my repo.

Refer:

• the new code options for SonarQube
• the new code options for SonarCloud
• the SonarCloud PR example

[aleksraiden]

@jihuayu thanks about your investigation, you are absolutely correct, I see a docs about sonar cube, not a cloud version.

[jihuayu]

@aleksraiden
Thank you for your help.
I am looking into this issue. Just a few more questions to deal.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarCloud

[PragmaTwice]

We are cleaning branches of this repo and this branch seems stale for a long time.

I'll close it and delete this branch. Feel free to submit a new patch if you want.

Also, if you want to keep these branches for a long time, you can push them into your own fork.