ExtAPI Developer guide

Continuous integration



ci-management project

jjb/externalapi/externalapi-nbi.yaml

https://gerrit.onap.org/r/#/c/87772/1/jjb/externalapi/externalapi-nbi.yaml

Sonar



https://sonar.onap.org/dashboard?id=org.onap.externalapi-nbi%3Anbi-rest-services

Sonar is activated in the jjb yaml file see continuous integration, there you can add or replace the target branch

See the jacoco maven plugin in pom.xml

To run test locally and avoid painful review/merge/jenkins very slooooow process just run ( enterprise proxy is optional..  )

mvn clean verify sonar:sonar -Dsonar.host.url=https://sonar.onap.org -Dhttp.proxyHost=127.0.0.1 -Dhttp.proxyPort=3128 -Dhttps.proxyHost=127.0.0.1 -Dhttps.proxyPort=3128

Versioning



oom project

oom env variable

https://gerrit.onap.org/r/#/c/87905/1/kubernetes/nbi/templates/deployment.yaml



And also edit live test which ensure instance is up in this values.yaml.. ( same url used by the healthcheck in integration project )

kubernetes/nbi/values.yaml

ex https://gerrit.onap.org/r/#/c/87462/2/kubernetes/nbi/values.yaml


integration project

version-manifest/src/main/resources/docker-manifest-staging.csv

version-manifest/src/main/resources/java-manifest.csv

Testing



integration/csit project

https://gerrit.onap.org/r/c/integration/csit/+/88772/1/tests/externalapi-nbi/healthcheck/healthcheck.robot


testsuite project

Used to play healthcheck

robot/resources/nbi_interface.robot

ex https://gerrit.onap.org/r/#/c/87630/1/robot/resources/nbi_interface.robot



http://onapci.org/logs/windriver-release-daily/2/report.html#tags?externalapi



https://gitlab.com/Orange-OpenSource/lfn/onap/onap-tests



https://jenkins.onap.org/job/externalapi-nbi-master-csit-healthcheck/



http://onapci.org/logs/windriver-release-daily/2/report.html#tags?externalapi



http://onapci.org/jenkins/job/windriver-release-daily/

Release process



First prepare staging

Remove SNAPSHOT from maven module

Update version to STAGING for docker

Play please release magic word in gerrit



Then update version references in oom and integration project ( to STAGING for docker.. ).



If OOM and integration run well ( wait 1h maybe to get full report ) you can proceed to release, by sending an email to heldesk

onap-helpdesk@rt.linuxfoundation.org <onap-helpdesk@rt.linuxfoundation.org>

Ask to tag both docker and java binaries, by adding jenkins logs ( which contains the binary uuid, since we are still in staging mode, a staging binary might be build several time.. ) and the final tag you want