[FOLIO-947] deploy registry-driven installation as folio-snapshot on AWS Created: 22/Nov/17 Updated: 12/Nov/18 Resolved: 29/Nov/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Jakub Skoczen | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint27 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 7 hours | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
TBD |
| Comments |
| Comment by Wayne Schneider [ 29/Nov/17 ] |
|
Posted to Slack (coreteam channel): This means that, for this system, if the interface moves ahead in the backend before the UI work is complete, the system should not break (fingers crossed). There is also a nightly folio/snapshot Vagrant box built from the same script (https://app.vagrantup.com/folio/boxes/snapshot). http://folio-testing.aws.indexdata.com will continue to track the tip of master for all components, UI and backend, as will the folio/testing and folio/testing-backend Vagrant boxes. For demo and other purposes, we could either try to resurrect folio-stable (based on released software, not CI-generated artifacts from the latest commits), now that the massive ui-users release is done (hooray, @mike!), or we could pursue the approach of "cloning" folio-snapshot when it passes regression tests. |
| Comment by Jakub Skoczen [ 29/Nov/17 ] |
|
Wayne Schneider my browser goes into a weird loop when I try to access folio-snapshots. |
| Comment by Jakub Skoczen [ 29/Nov/17 ] |
|
Works after a forced refresh. |
| Comment by Wayne Schneider [ 29/Nov/17 ] |
|
Jakub Skoczen – I think this is the result of
|