Architecture
Jenkins (and probably JJB) will be used for all CI/CD purposes.
Follow the guide https://jenkins.io/doc/book/installing/ to setup Jenkins in the local lab.
Each POD will be connected as a Jenkins slave node to a local Jenkins server node in the current lab
The Jenkins GUI is http://159.138.47.166:8080
Pipelines
ELIOT Verify jobs (on patch submission affecting the code in ELIOT repo) - i.e. linting input YAML/bash/python on patch submission(DONE)
ELIOT deployment testing
ELIOT Daily jobs (scheduled to run recurrently)
- Deploy ELIOT
- Run testing suites
- Collect logs and publish them to Akraino Nexus Repo https://nexus.akraino.org/#view-repositories;logs~browsestorage
ELIOT Documentation building (on documentation patch submission for peer review) and publishing (on documentation patch merge)
Artifacts
- Documentation
- Installation scripts (the main ELIOT repository : https://gerrit.akraino.org/r/#/admin/projects/eliot)
- Test logs and results
Jenkins Jobs
Verify: https://jenkins.akraino.org/view/eliot/job/eliot-master-verify/
we have two daily jobs and we are going to add a job to run ELIOT on Centos
Daily: http://159.138.47.166:8080/job/eliot-deploy-k8s-virtual-daily-master/
http://159.138.47.166:8080/job/eliot-deploy-kubeedge-virtual-daily-master/