Re: Moving from sonar.opendaylight.org to Sonarcloud.io


Anil Belur
 

Greetings Robert:

Trying to catch up on where we are with the sonarcloud migrations. I think another issue has been identified with 0% coverage, that is caused by an update on the Java analyzer. 
With sonarcloud it's no longer possible to import jacoco.exec reports, and the workaround suggested is to use XML format. This needs to be fixed in the pom files.

Example on how this is fixed on an external project:
https://github.com/synyx/urlaubsverwaltung/pull/930/files

Thanks,
Anil


 
 



On Fri, Dec 13, 2019 at 8:01 AM Eric Ball <eball@...> wrote:
At this point, what's still needed before we start merging these changes? I can continue to address any concerns with this, but if there isn't anything further, I'd like to start getting these changes reviewed and merged. https://git.opendaylight.org/gerrit/q/status:open+sonarcloud

On Mon, Dec 9, 2019 at 1:50 PM Robert Varga <nite@...> wrote:
On 09/12/2019 22:36, Eric Ball wrote:
> Ok, I've recreated the "ODL way" Java quality profile (59 of 60 rules;
> one was deprecated) in Sonarcloud, and set it as the default. Future
> runs should reflect only those rules that were chosen. I still think
> this should probably be updated, as it has not changed in 5 years, but
> for now the results should be closer to what you're getting in SonarQube.

Yeah, I was going to write that, but haven't gotten to it. We certainly
should take the default sonarcloud profile and re-evaluate it.

Regards,
Robert



Join TSC@lists.opendaylight.org to automatically receive all group messages.