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

Compare with Current View Page History

« Previous Version 4 Next »

Repositories

Code is contained within the following Git repositories.

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.

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...


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.

ComponentJobs
Common
Context Aggregator
AAI Context Builder
SDC Context Builder
SDNC Context Builder
Network Discovery Context Builder

Nexus

Artifacts produced by build jobs – e.g. Docker images – are stored in Nexus.

https://nexus3.onap.org

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.)




  • No labels