[FOLIO-2118] CI-integrated continuous deployment (Q2, cluster setup) Created: 26/Jun/19 Updated: 03/Jun/20 Resolved: 02/Jul/19 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Umbrella | Priority: | P3 |
| Reporter: | Wayne Schneider | Assignee: | Jakub Skoczen |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, platform-backlog, q2-2019, sprint49, sprint50, sprint51, sprint52, sprint53, sprint54 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Sprint: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Development Team: | Core: Platform | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Description |
|
(this issue has been split from
Problem statementCurrent FOLIO CI infrastructure and reference environments have several limitations that make it hard to scale them the point where a fully continuos and isolated deployment of development builds (e.g from PRs and feature branches, for both UI and backend modules) is possible. Those limitations include:
This is makes it impossible to implement certain development process capabilities (like the PR previews, see
Proposed approachWe would like to revamp the deployment and orchestration infrastructure, create a new, clustered and multi-tenant, reference environment for development and integration purposes, and update the CI processes (Jenkins, Ansible, etc) to allow for a more continuos and isolated deployment of development artefacts. OrchestrationBased on the prior work from from Jason Root (TAMU) and Mark Stacy (Core: platform/Colorado, see
The Core: platform has undertaken a focused effort to ease K8s integration across FOLIO platform. This effort is tracked on
Clustered reference environmentThis work is being done outside of the Platform team, see
CI processWe would like to extend the CI process in a way which allows to:
See
Further read PR previews:
|