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


Eric Ball <eball@...>
 

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.

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:


On 13/11/2019 01:28, Anil Belur wrote:
> Hi Abhijit: 
>
> Please add this thread to the week's TSC call agenda and possibly take a
> vote on this. 
>
> 1. ODL Projects needs to vote (+1) before each of these change can be
> merged on releng/builder.
>     https://git.opendaylight.org/gerrit/c/releng/builder/+/85644

That patch has been abandoned for a per-project migration (on Andy's
request).

Furthermore, as I noted in the review, we really should duplicate the
sonar jobs, so we can actually evaluate how the projects work with
SonarCloud before ...


> 2. Agree upon a time when Sonarcube (https://sonar.opendaylight.org
> <https://sonar.opendaylight.org/>) can be decommissioned. Please note,
> Sonarcloud has better features and language support than SonarQube, and
> also remove the hosting and maintenance costs associated with the
> SonarQube server.

... we decide on this.

Regards,
Robert



>
> Thanks,
> Anil
>
> On Thu, Nov 7, 2019 at 8:02 AM Eric Ball <eball@...
> <mailto:eball@...>> wrote:
>
>     Hello all,
>
>     We here at the LF Release Engineering team are working on a move
>     from hosted SonarQube instances to the cloud-based Sonarcloud
>     service. To that end, there is currently a proposed change to all
>     Sonar jobs that would move them to
>     Sonarcloud: https://git.opendaylight.org/gerrit/c/releng/builder/+/85644
>
>     Sonarcloud has more features and better language support than
>     SonarQube, and it will remove the hosting and maintenance costs
>     associated with the SonarQube server. Our plan is to decommission
>     the SonarQube server about a month after we make the move to Sonarcloud.
>
>     You can view the OpenDaylight Sonarcloud page
>     here: https://sonarcloud.io/organizations/opendaylight/projects
>     Currently, the only projects showing results are those that have run
>     and passed on the sandbox. Once the change is merged, all projects
>     will show results after their next successful run.
>
>     You may notice that while quantitative numbers like code coverage
>     and duplication haven't changed, the number of
>     bugs/vulnerabilities/code smells may have changed significantly
>     (most likely an increase). This is due to Sonarcloud using much more
>     up-to-date Quality Profiles than ODL's SonarQube instance, so this
>     should be considered an improvement in results (even though I
>     understand that it can be a pain to suddenly have a backlog of
>     issues where there were few or none before). These profiles can be
>     customized, so if anyone sees something coming up that absolutely
>     should not be in the results, we can remove it from the Quality Profile.
>
>     Please let me know if you have any questions, or if you'd like to
>     bring this up for discussion during the next TSC meeting.
>
>     Note: ovsdb is using a custom Sonar template. This will need to be
>     changed to work with Sonarcloud, or (preferably) changed to use
>     global-jjb templates. If there's something our global-jjb jobs do
>     not currently support, we should be able to add that functionality.
>
>     Eric Ball
>     Release Engineer
>     The Linux Foundation
>     -=-=-=-=-=-=-=-=-=-=-=-
>     Links: You receive all messages sent to this group.
>
>     View/Reply Online (#12181):
>     https://lists.opendaylight.org/g/TSC/message/12181
>     Mute This Topic: https://lists.opendaylight.org/mt/44622856/1278122
>     Group Owner: TSC+owner@...
>     <mailto:TSC%2Bowner@...>
>     Unsubscribe: https://lists.opendaylight.org/g/TSC/unsub 
>     [abelur@... <mailto:abelur@...>]
>     -=-=-=-=-=-=-=-=-=-=-=-
>
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12218): https://lists.opendaylight.org/g/TSC/message/12218
> Mute This Topic: https://lists.opendaylight.org/mt/44622856/1320659
> Group Owner: TSC+owner@...
> Unsubscribe: https://lists.opendaylight.org/g/TSC/unsub  [nite@...]
> -=-=-=-=-=-=-=-=-=-=-=-
>

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