[FOLIO-2497] Migrate release reference builds to K8s Created: 03/Mar/20 Updated: 02/Sep/20 |
|
| Status: | Blocked |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||
| Sprint: | |||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||
| Description |
|
Migrate release reference builds from dedicated ec2 instances to K8s. This includes daily builds of 'folio-release' and 'folio-release-core' which are taken from the master branches of platform-complete and platform-core as well as quarterly release branches for each repository starting with the Q2-2020 fameflower release. |
| Comments |
| Comment by Jakub Skoczen [ 06/Mar/20 ] |
|
Note: we need to consider if Okapi can be fully backwards compatible with older FOLIO releases. If not this may required an isolated namespace. Adam Dickmeiss |