Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 4 Next »

The following items are expected to be completed for the project to Pass the M3 API Freeze Milestone.

M3 Release Architecture Milestone overview is available in wiki.

Practice AreaCheckpointYes/NoEvidencesHow to?
Architecture


Has the Project team reviewed the APIs with the Architecture Committee (ARC)?In Progress

Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough.

Is there a plan to address the findings the API review?NA
The plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wiki.
Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval?YES
In the case some changes are necessary, bring the request to the TSC for review and approval.

Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone?

NO
Critical point to understand is that change is inevitable, and that right timing and clear communication to the community will ease the process of accepting changes.
Provide link to the API Documentation.YES

API Design document & swagger are available

API Listener swagger

API ServiceOrder swagger

Design document


Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?YES

All 6 stories are done

Link to stories in JIRA


Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?NA

Have all findings from previous milestones been addressed?NAProvide link to JIRA findings
DevelopmentIs there any pending commit request older than 36 Business hours in Gerrit?NO

Do you have a plan to address by M4 the Critical  and High vulnerabilities in the third party libraries used within your project?YES

EXTAPI-126 - Getting issue details... STATUS

Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo.

Are all the Jenkins jobs successfully passed ( Merge-Jobs)?

YES

Jenkins externalapi

Git externalapi/nbi

Sonar Line coverage = 69%


Are all binaries available in Nexus?

JAR in nexus

Docker in nexus


Integration and Testing

Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins?

NANo integration test
Has the project code successfully passed the Daily Build process?YES

Both java an docker daily build

https://jenkins.onap.org/view/externalapi/

Goal is to ensure the latest project commit has not broken the Integration Daily Build 
  • No labels