Table of Contents
outline true

Introduction

ICN Pod Topology

Jenkins Information

...

Table of Contents
outline true

Introduction

ICN Pod Topology

Jenkins Information

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.

...

To add more Jenkins slave nodes, please follow the akriano jenkins guide

To setup private jenkins, please refer to the README.md under icn/ci/

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

...

Overall Test Architecture

Test Architecture

We support the following  jobs

CI job for golang

• triggered by gerrit patch creation/update. 
• Run a make command, which builds golang pkg
• Post +1/-1 for gerrit patch if the build succeeds/fails

...

We support the following  jobs

CI job

• triggered by gerrit patch creation/update. 
• Run a make command, which runs bashate to check shell scriptsThe 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 check passes/failsbuild succeeds/fails
• Upload 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:

...

Baremetal deployment

Virtual deployment

Test Framework

All components are tested with end-to-end testing

...