Timeline of events (These are still under discussion with the community and might change. Please look at the comments)
- Update oparent to remove SonarQube plugin and configure Jacoco https://gerrit.onap.org/r/#/c/oparent/+/98687/ (ETA Nov 22)
- Make an oparent release wit this change (ETA Nov 22)
- Present the teams with next steps to complete the table below (ETA Nov 25)
SonarCloud migration notes
Ready to migrate? Things to consider and challenges faced with the currently migrated teams
- Teams will still be using the same Jenkins jobs
- SonarCloud is based on SonarQube 8.0 with +- some feature and plugin differences
- SonarQube will stay around for some time, but eventually will be deprecated (mid next year)
- Warnings in Quality Gates are no longer applicable in SonarCloud
- Teams using the "org.sonarsource.scanner.maven" plugin, might face issues during the migration since this plugin calls SonarQube directly.
- Releng will report these issues from the testing
- Teams will need to disable this plugin and configure jacoco like ODL does https://github.com/opendaylight/aaa/blob/master/pom.xml#L58-L93
- APPC example of this: https://gerrit.onap.org/r/#/c/appc/+/98197/
Changes needed to be done and stakeholders
RELENG: Modify project's yaml files to run Sonar on SonarCloud
RELENG: Test new runs in Sandbox and report failures
TECHTEAM: If failures are reported from the test, techteams help will be needed (Most likely related to dependencies and SonarQube specific plugins in the source)
TECHTEAM: Once test passes, review the final report and +1 Releng ci-management change
RELENG: Merge ci-management change
Testing the migration
The reports will now be posted under: https://sonarcloud.io/organizations/onap/projects
Jenkins jobs do not change.