Re: Moving from sonar.opendaylight.org to Sonarcloud.io
Eric Ball <eball@...>
toggle quoted message Show quoted text
To get this moving again, I've tested all of the Sonar jobs that are currently passing for SonarQube on the prod Jenkins. There were a few failures, but they appear to be related to something missing from the sandbox (presumably credentials, though I'm not familiar enough with the jobs to say for sure. Any assistance would be appreciated), since the SonarQube versions of the jobs that pass on prod also fail (I labeled the runs of these jobs as "Sonarcloud build" and "SonarQube build" for clarity. All passing jobs are Sonarcloud). The fact that they all work the same is no surprise; moving from SonarQube to Sonarcloud makes essentially no difference to how the scans work. It's really just a change of where the results are going.
Sonar testing on the sandbox: https://jenkins.opendaylight.org/sandbox/view/All-Sonar/
For comparison, Sonar jobs on prod: https://jenkins.opendaylight.org/releng/view/All-Sonar/
To view (and hopefully review) the open code changes, please see here:
On Wed, Nov 13, 2019 at 12:51 AM Robert Varga <nite@...> wrote: