Table of Contents
outline true

Introduction

...

Jenkins Information

ICN project leverages Akriano Akraino community has a public Jenkins cluster. ICN leverages the Akriano public Jenkins to run CI jobs. But we run While the CD jobs run in our private Jenkins cluster.

We have the following Jenkins slave nodes joined Akriano Jenkins. ICN CI jobs are supposed to be scheduled to our slave nodes by label icn-dev.

...

The private jenkins cluster is setup on pod14-node2. We can visit the jenkins with the node ip address: http://10.10.140.22:8080/

Currently we support only AIO private Jenkins.

Akarino Test Group Information

...

We support the following  jobs

CI job

...

• triggered by gerrit patch creation/update. 
• Run a make command, which builds golang pkgThe job runs verify.sh under icn project. The verify.sh currently has integrated the golang test and bashate test.
• Post +1/-1 for gerrit patch if the build succeeds/fails

CI job for shell

• triggered by gerrit patch creation/update. 
• Run a make command, which runs bashate to check shell scripts
• Post +1/-1 for gerrit patch if the check passes/failsUpload the job log to Nexus server in post-build actions

CD job for test

• triggered daily automatically (We can also trigger it manually)
• Run a make command, which creates VM(s) and deploys ICN components on the VM(s)
• Send daily report to mailing listUpload the job log to Nexus server in post-build actions

CI jobs detail

Image RemovedUpdate the verify.sh can update the CI job content.

Image Added

CD job detail

We have the following steps for CD job:

...

Virtual deployment

Test Framework

All components are tested with end-to-end testing

...