You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

TaskAdd SonarCloud variables in project's yaml files 

Remove SonarQube plugin if RelEng test fails

(org.sonarsource.scanner.maven)

Review resultsComment on progress
ResponsibleRelEngPTLPTL
Estimated Duration15 min
per project (including sandbox test and reviews)
10 min per project including reviews10 min per report
AAF



AAI



APPC



CCSDK



CLAMP



CLI



DCAE



Demo



DMAAP



ExtAPI



Holmes



Integration



Logging



Modeling



MSB



MultiCloud



Music



OOF



OOM



O-parent



Policy



Portal



SDC



SDNC



SO



UUI



VFC



VID



VNFSDK



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.

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.


  • No labels