Repositories
Code is contained within the following Git repositories.
| Component | Repository |
|---|---|
| Common | https://git.onap.org/logging-analytics/pomba/pomba-audit-common/ |
| Context Aggregator | https://git.onap.org/logging-analytics/pomba/pomba-context-aggregator/ |
| AAI Context Builder | https://git.onap.org/logging-analytics/pomba/pomba-aai-context-builder/ |
| SDC Context Builder | https://git.onap.org/logging-analytics/pomba/pomba-sdc-context-builder/ |
| SDNC Context Builder | https://git.onap.org/logging-analytics/pomba/pomba-sdnc-context-builder/ |
| Network Discovery Context Builder | https://git.onap.org/logging-analytics/pomba/pomba-network-discovery-context-builder/ |
| AAI Data Router | https://git.onap.org/aai/data-router/ |
| AAI Search Data Service | https://git.onap.org/aai/search-data-service/ |
| AAI Validation Service | https://git.onap.org/aai/validation/ |
| OOM | https://git.onap.org/oom/ |
Branches
The 'master' branch is for the release currently in progress. There are alternate branches for past releases. (e.g. 'Casablanca').
Code Submission
Information on how to utilize Git and Gerrit to submit new code is available here: Configuring Gerrit.
Tips on code submission best practices are available here: Commit Messages.
When submitting to non-core POMBA repositories, it's helpful to label the submission with 'pomba', both for ease of filtering and batch reviewing.
Code Reviews
Code reviews are performed in Gerrit.
| Component | Code Reviews |
|---|---|
| Common | https://gerrit.onap.org/r/#/q/project:logging-analytics/pomba/pomba-audit-common |
| Context Aggregator | https://gerrit.onap.org/r/#/q/project:logging-analytics/pomba/pomba-context-aggregator |
| AAI Context Builder | https://gerrit.onap.org/r/#/q/project:logging-analytics/pomba/pomba-aai-context-builder |
| SDC Context Builder | https://gerrit.onap.org/r/#/q/project:logging-analytics/pomba/pomba-sdc-context-builder |
| SDNC Context Builder | https://gerrit.onap.org/r/#/q/project:logging-analytics/pomba/pomba-sdnc-context-builder |
| Network Discovery Context Builder | https://gerrit.onap.org/r/#/q/project:logging-analytics/pomba/pomba-network-discovery-context-builder |
| AAI Data Router | https://gerrit.onap.org/r/#/q/project:aai/data-router |
| AAI Search Data Service | https://gerrit.onap.org/r/#/q/project:aai/search-data-service |
| AAI Validation Service | https://gerrit.onap.org/r/#/q/project:aai/validation |
Committers
Make sure to add appropriate committers (as well as reviewers) to submissions so that they can provide them with "+2" reviews, allowing for a merge to be done.
Note: For some projects (and maybe more in the future), comitters may not be from the same company as the submitter.
| Project | Committers |
|---|---|
| POMBA | |
| SDNC | |
| AAI | Steve Blimkie |
| OOM |
Note: Comitters are subject to change so make sure you're up to date!
Gerrit Commands
Refer to Development Procedures and Policies#MagicWords for information about special "replies" that can be used to invoke actions.
Build Jobs
Verify Jobs
The verify jobs are engaged when code is submitted to the repository in order to confirm builds wouldn't break due to the inclusion of the change.
'ONAP Jobbuilder' events will appear in the Gerrit review.
Merge Jobs
The merge jobs are engaged when a committer allows a code change to be added to a branch in the repository.
Docker Jobs
The Docker jobs build docker images and upload them to Nexus.
Release Jobs
...
Sonar Jobs
The Sonar jobs perform a code-quality scan of the repository to ensure that best practices are adhered to and vulnerabilities are addressed.
Nexus
Artifacts produced by build jobs – e.g. Docker images – are stored in Nexus.
Sonar Reports
Sonar provides a dashboard of metrics related to code repositories that should be checked to ensure that quality thresholds are being met.
Line Coverage
Each project institutes a certain threshold for line coverage that must be upheld. If code submissions result in line coverage dipping below this threshold, this will eventually be noticed and cause trouble for the developers. (In Dublin Logging, the threshold is 50% but this is subject to change.)
After completing work on a story or bug, Line Coverage should be checked to ensure that thresholds are met. (It's best to have higher coverage than required in order to be able to accommodate future code submissions, particularly if/when the current threshold is raised.)