...
| Jira No | Summary | Description | Status | Solution |
|---|---|---|---|---|
Jenkins, Gerrit and Sonar – Thierry Aleno | Master branch content only is analyzed only by SonarCloud. WikiMedia solution was tested and is based on Sonar Webhook and small web service hosted on Toolforge. Developer proposes a patch on Gerrit, Jenkins job is triggered with patch set event, in the Jenkins job the analysis of the proposed code is launched in SonarCloud, Jenkins job goes to the end if Maven build is ok, we have a very at +1, if failed: verify at -1. after in the endof analysis of the code in SonarCloud, Webhook posts a request with the result of the scan to the web service which gets the request and if the name of the branch is Master, does nothing, if the name of the brach is short life branches, sends +1 in the verify parameter if the scan is OK, and 0 if the scan is NOK - in this case parameter in the gerrit is removed and developer has to correct his/her code before proposing this patch. Patch can not be merged into the branch. When gerrit receives the post request sent by the web service (containing verify parameter + which conditions are OK and which are NOK). Webservice developped by Wikimedia can be adapted (some URL hardcoded) and to be tested with SonarCloud.io. Estimated LoE (Level of Effort) is very small. For ONAP quality gate is very low: https://sonarcloud.io/organizations/onap/quality_gates/show/6826 | ongoing | Meeting to be organized by Pawel with LFN (Jess, Kenny) and friendly project (CPS) for a PoC later this week. If result of the PoC is positive, it could be generalized to whole ONAP. We should present the solution to PTLs. Use cases for a PoC to be defined. | |
| PTLs meting update |
| ongoing | PTLs shall be encouraged to take their actions to deprecate their relevant repos. | |
| TSC meeting update | TSC approved SonarCloud profile management model. Invitation received from Bengt to ONAP GitHub | ongoing | GitHub IDs to be collected from PTLs - to be checked with David by Pawel. Amy to follow-up with Bengt directly on being added to ONAP GitHub. | |
| (IT-22048) for direct vs. indirect dependencies with container scans | Feedback from Bengt to move on with ticket at Sonatype by opening a feature request - Amy opened a feature request (IT-22175) - no update | ongoing | ||
| Fabian's update - quality of a code | DMaaP only 16 minor security issues, with SO pending merge (e-mail was sent to Seshu - no response so far, but Fabian reports merge) | ongoing | E-mail to be sent to Seshu to try to move forward merge (Pawel). Meeting to be organized with Jess and LFN on plugin deployment possibility (Fabian) | |
| Software BOM and point upgrade discussion – atomic level of ONAP. | How detailed BOM shall be. Release Management of a different ONAP components - way to collect information ( ajor ONAP modules, OSes, DBs etc.). Software Bill of Materials - we do not crreate today but we have Nexus-IQ from which information can be retrieved. Contractural aspects to be checked. How to upgrade vulnerable module? | started | Amy to organize with Muddasar a meeting on Software BOM. | |
| OUR NEXT SECCOM MEETING CALL WILL BE HELD ON 6th OF JULY'21. | Continuation on atomic level of ONAP discussion. |
Recording:
| View file | ||||
|---|---|---|---|---|
|
SECCOM presentation: