Overview
This page is to provide detail on the contribution process for CPS.
Code Repo
https://gerrit.onap.org/r/admin/repos/cps
Initial Seed Code Contribution
Code Requirements
- Copyright included in each file. Apache 2 for coding files.
- The Copyright line for contributing organization inserted or updated reflecting the contribution year.
- A LICENSE.txt file placed at the root of the repo to provide umbrella coverage.
- Unit testing coverage > 55% for POC
- We will follow ONAP Recommended Software Development Best Practices: Developer Best Practices
https://jira.onap.org/secure/RapidBoard.jspa?projectKey=CPS&rapidView=228
JIRA Status Updates
Move To | When |
|---|---|
| In-progress | The moment you start working on it. |
| Submitted | The review is merged, merge & CICD jobs are successful. |
| Closed | Documentations are updated. Complete demo to team. |
Committer Strategy
- Each review requires 2 committers to +1 and +2.
- A +2 from committer or PTL have the permissions to merge code.
Code Submissions
- Any checkstyle issues must be fixed in current review.
- Code must be covered by tests.
- Mark the review as WIP if it is not ready for review.
- Commit message must be in the following format:
Comment explaining what is the purpose of the code. Issue-ID: CPS-1 Jira Link: https://jira.onap.org/browse/CPS-1 |
Java Code Required Practices
WIP
Jenkins Job
ONAP uses Jenkins based CICD tool chain. However, contributors are only given read access to the Jenkins servers. All jobs are created by automatic generation from JJB definitions.
https://jenkins.onap.org./view/cps/
Bug reporting
Vulnerability report process
Contact PTL ; toine.siebelink@est.tech