Objective: Involves setting up automated pipelines that ensure every code change made in eoAPI is automatically tested and reliably deployed into the production environment. The focus will be on enhancing code quality, reducing manual errors, speeding up the release process, and ensuring the high availability and stability of eoAPI. Implementing CI/CD practices aims to streamline development workflows, facilitate quicker iterations, and enable a more agile response to the needs of users and stakeholders.
Lead contributor: DevSeed
Priority: 1
Upper Bound Estimate: 7
Lower Bound Estimate: 5
Requirements:
None
Implementation
Ideally the V&V plan / tests should be maintained in a single place but feature in the EOEPCA building block docs in https://github.com/EOEPCA/data-access.
However, docs integration is secondary. First step is to create the content: what tests (will) exist in eoapi-k8s and how do they run? Could be in eoapi-k8s README or so first.
Where to document is not settled yet:
We do not have a template for the V&V plan.
I agree it is a good idea to include it within the main BB doc - but perhaps we need an additional Testing heading under Administration for this.
Our tests will also need to run in the system end-to-end test suite:
Implementation
Ideally the V&V plan / tests should be maintained in a single place but feature in the EOEPCA building block docs in https://github.com/EOEPCA/data-access.
However, docs integration is secondary. First step is to create the content: what tests (will) exist in eoapi-k8s and how do they run? Could be in eoapi-k8s README or so first.
Where to document is not settled yet:
Our tests will also need to run in the system end-to-end test suite:
Quarterly breakdown