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 2 Next »

Architecture

Jenkins (and probably JJB) will be used for all CI/CD purposes.

Each POD will be connected as a Jenkins slave node to one public Jenkins master node or to a local Jenkins master node in the current lab (TBD).

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(TBD)

ELIOT Daily jobs (scheduled to run recurrently)

  1. Deploy ELIOT 
  2. Run testing suites
  3. Collect logs and publish them (e.g. on Google storage)

ELIOT Documentation building (on documentation patch submission for peer review) and publishing (on documentation patch merge)(TBD)


Artifacts

  • Documentation
  • Installation scripts (the main ELIOT repository)
  • Test logs and results

Jenkins Jobs

Daily: https://jenkins.akraino.org/view/eliot/job/eliot-master-verify/

  • No labels