Info |
---|
SONARQUBE SUPPORT WILL END FEB-20Please make sure there are no components left in SonarQube Please implement SonarCloud coverage drop fix explained below |
Timeline of events
To prevent dependency issues, this migration is planned to happen in 2 stages.
Stage 1 will use hardcoded sonar goals to the needed plugin version to avoid waiting on dependencies from where this can be inherited.
Stage 2 will be a cleanup stage and work towards fixing the plugin in the dependencies like oparent and slowly migrate teams to it while removing hardcoded sonar goals.
STAGE 1
- RELENG → Will add the needed changes in ci-management for each project and run a test in the sandbox
- RELENG → will post the restults of the sandbox test in the 3rd column below.
- This is not reflecting if the Sonar report actually pass or failed a quality gate. Instead, this result is the outcome of running the Sandbox job using the changes in ci-management.
- TECHTEAM → Review the results and comments posted by Releng in column 4. PTLs will be mentioned explicitly to notify them that the next action is on their team.
- TECHTEAM&RELENG → Will work on any additional comments/questions/issues from column 4 and 5.
Timeline of events (These are still under discussion with the community and might change. Please look at the comments)
...
Info |
---|
SONAR COVERAGE DROP TO 0%Sonar Cloud made an update on the jacoco plugin where they dropped support for .exec file format. We need to use .xml instead. Please look for more information in https://community.sonarsource.com/t/sonar-coverage-dropping-to-0-for-some-projects/18521/2 Some teams like APPC have upgraded their reports and coverage was restored for them. Please follow their examples: |
...
...
...
Tableenhancer |
---|
numberOfFixedRows | 3 |
---|
decimalMark | . (point) |
---|
|
Task | Add SonarCloud variables in project's yaml files | Sandbox test |
---|
Remove SonarQube plugin if RelEng test fails (org.sonarsource.scanner.maven)of my change (DO NOT CONFUSE WITH SONAR REPORT RESULT) | Review results | Comment on progress |
---|
Responsible | RelEng | Releng | PTL |
---|
PTL |
|
---|
Estimated Duration | 5 min | 15 min to 1 hr depending |
---|
10 min per project including reviewsfailed | PASS | Takamune Cho This is marked as "PASS" becuase the build actually produced the same result as what we had in SonarQube, but I know we still are facing coverage issues. Shall we merge this change to move to SonarCloud and continue our investigation there? Jessica Wagantall I +1 already. we still have to work with the issue. I have posted my last comment on IT-17899. Please take a look. thx | Coverage drop still low, we are taking our investigation to SonarCloud but the migration is completed
Issue has been fixed. back to 80% | CCSDK parent needs to migrate firstmost passWorking with Dan to migrate ccsdk-parent1/2 pass for JDK13 but having issues with JavaScript (Contacted Sonar team)most failed | PASS | Morgan Richomme Gerrit ready, SonarCloud results pushed and waiting on committers to +1 my change if all looks ok | failfailfailfail | PASS | Hui Deng Gerrit ready, SonarCloud results pushed and waiting on committers to +1 my change if all looks ok Completed | Completed | fail | PASS | Huabing Zhao Gerrit ready, SonarCloud results pushed and waiting on committers to +1 my change if all looks ok Completed | Completed | failfailci-management98558most fail | Passmost passVID team might need to configure their reports in the jacoco plugin (Please look at the comment section)Waiting on Tech team to review reports.most pass
|
STAGE 2
- Update oparent to upgrade the sonar plugin and Jacoco configuration to the latest plugin required by SonarCloud: https:/
...
- /sonarcloud.io/documentation/analysis/scan/sonarscanner-for-maven/
- Make an oparent release wit this change
- Migrate teams to the new oparent while also removing the hardcoded goals in their sonar ci-management changes from the above table
...
SonarCloud migration notes
...
- 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 .in older versions.
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
...
Testing the migration
The reports will now be posted under: https://sonarcloud.io/organizations/onap/projects
...