[FOLIO-694] Assess folio-stable/testing retention Created: 26/Jun/17 Updated: 12/Nov/18 Resolved: 13/Sep/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, cicd, for-next-sprint, sprint18 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 hour | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
Currently we have daily backend folio-testing and folio-stable builds as well as more frequent updates to the front-end UI components. UI regression tests are run on each platform once per day. The current CI build process is changing the configuration of the platform frequently - particularly folio-testing. We should determine if the retention time for folio-testing (and maybe folio-stable) is appropriate and whether we should increase the retention time or maintain a set of multiple builds for some determined length of time. |
| Comments |
| Comment by Jakub Skoczen [ 26/Jul/17 ] |
|
folio-staging – a staging system for folio-stable folio-testing-working – a last successful/working build of folio-testing |
| Comment by John Malconian [ 13/Sep/17 ] |
|
Closing this until we decide there is an actual need to deviate from our current workflow. |