[FOLIO-754] Create folio/stable v3.0.0 Created: 01/Aug/17 Updated: 12/Nov/18 Resolved: 09/Aug/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P2 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint19 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 day, 2 hours | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
Update with new minor releases for Okapi, mod-permissions, mod-users, mod-login, mod-authtoken, mod-circulation, mod-circulation-storage, test data for circulation |
| Comments |
| Comment by Wayne Schneider [ 01/Aug/17 ] |
|
Able to build stable-backend with new releases, but an attempt to build a full stack system resulted in a regression with loan history. Testing stable-backend against a stripes bundle built from HEAD of master resolves the issue, so we clearly need some releases of frontend components to build a stable distribution. |
| Comment by Wayne Schneider [ 03/Aug/17 ] |
|
Currently waiting for releases of stripes-core and mod-users-bl |
| Comment by Wayne Schneider [ 04/Aug/17 ] |
|
I'm able to build a stable system in Vagrant that passes all UI tests. Was unable to deploy to folio-staging, however – the stripes-staging Jenkins job failed with the error: [vagrant] Running shell script + vagrant up stripesstaging The machine with the name 'stripesstaging' was not found configured for this Vagrant environment. |
| Comment by John Malconian [ 04/Aug/17 ] |
|
Some weirdness with the Vagrant 'vagrant-nodes' config file. I've committed an updated version and run the build successfully. All regression tests pass. |