[FOLIO-820] Build stable release 4.0.0 Created: 02/Sep/17  Updated: 12/Nov/18  Resolved: 14/Sep/17

Status: Closed
Project: FOLIO
Components: Continuous Integration
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: Wayne Schneider Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: 1 day, 4 hours, 15 minutes
Original estimate: Not Specified

Issue links:
Relates
relates to UIU-203 Unsaved Changes Modal Display When it... Closed
Sprint:

 Description   

This release will encompass work from sprint 20 and sprint 21.



 Comments   
Comment by Wayne Schneider [ 04/Sep/17 ]

Software versions installed:
Okapi v1.10.0
mod-authtoken v0.6.1
mod-permissions v4.0.4
mod-login v3.1.0
mod-configuration v2.0.0
mod-users v14.2.0
mod-users-bl v2.0.2
mod-inventory-storage v5.1.0
mod-inventory v5.1.1
mod-circulation-storage v3.2.0
mod-circulation v4.4.0
mod-notes v0.2.0
mod-notify v0.1.1
ui-users v2.10.0
ui-items v1.11.0
ui-checkout v1.1.2
ui-checkin v1.1.1
ui-requests v0.0.1
ui-circulation v1.1.1
ui-organization v2.2.0
ui-developer v1.3.0
ui-plugin-example v0.2.0
ui-plugin-find-user v1.0.0
stripes-components v1.7.0
stripes-core v2.7.0

Comment by Wayne Schneider [ 04/Sep/17 ]

folio-staging is now up with the latest released versions of all components. The ui-testing suite of tests v4.1.0 fails on trying to delete patron groups with these errors:

1) Module test: users:patron_group Login > Add new patron group > Assign to user > Try to delete patron group > Unassign from user > Try to delete again > Logout
 should fail at deleting "Alumni" group:
     Error: done() invoked with non-Error: Unable to find element by selector: a[href="/settings/users"]
      at process._tickCallback (internal/process/next_tick.js:109:7)

  2) Module test: users:patron_group Login > Add new patron group > Assign to user > Try to delete patron group > Unassign from user > Try to delete again > Logout
 should delete "Alumni" patron group:
     Error: done() invoked with non-Error: Unable to find element by selector: id("ModuleContainer")//a[.="Users"]
      at process._tickCallback (internal/process/next_tick.js:109:7)

The process appears to work correctly when you do it manually in the interface, so perhaps the tests and the released versions aren't lined up entirely correctly.

Comment by Wayne Schneider [ 05/Sep/17 ]

Errors have to do with a modal popup that appears to be erroneous when you edit a user. It's possibly a stripes-form issue (v0.8.0 released June 30, it's pretty old).

Comment by Wayne Schneider [ 05/Sep/17 ]

The stripes-form release (v0.8.1) took care of the modal, but there is an issue with timeouts in the new_user test. A new release of ui-users will contain updated tests, we'll use that to build a new ui-testing Docker image.

Comment by Wayne Schneider [ 05/Sep/17 ]

Removed ui-requests from the build, as the released version (v0.0.1) no longer works with the latest released stripes libraries.

Comment by Wayne Schneider [ 05/Sep/17 ]

folio-staging and folio-stable have been updated and pass all UI tests. folio/stable and folio/stable-backend Vagrant boxes released.

Comment by Wayne Schneider [ 06/Sep/17 ]

Buttons for proxy user functionality have the wrong icon. Maybe need a new release of ui-plugin-find-user?

Comment by Wayne Schneider [ 06/Sep/17 ]

It appears that setting up a system with all released components + the HEAD of master for ui-plugin-find-users fixes the problem. I will ask for a release of ui-plugin-find-users.

Comment by Wayne Schneider [ 06/Sep/17 ]

A build with the newly released ui-plugin-find-user v1.1.0 fixes the problem. folio-stable has been updated, and a new version of the folio/stable Vagrant box (v4.1.0) is being released.

Comment by Wayne Schneider [ 08/Sep/17 ]

Waiting for Charlotte Whitt/Cate Boerema to give the go-ahead to make this folio-demo.aws.indexdata.com

Comment by Cate Boerema (Inactive) [ 08/Sep/17 ]

Is there a reason we aren't including Requests? I'll poke around a bit more

Comment by Wayne Schneider [ 08/Sep/17 ]

Requests are not included because the software is not in a released state (it's still in a snapshot state). If we want it included, I can work with Matt Connolly to get a 1.0.0 release that works with the other released software (it's currently at version 0.0.1).

Comment by Cate Boerema (Inactive) [ 11/Sep/17 ]

Okay, no need to get Requests in now. That said, I have a demo on Wed September 27th at 11 am ET and I'd love to have a stable environment available for that, ideally with Requests available. is that possible? I will add the date and time to our team calendar.

Also, I thought folio-demo was deprecated. Is it not? What is the difference between folio-stable and folio-demo?

Comment by Wayne Schneider [ 11/Sep/17 ]

My understanding is that folio-testing.aws.indexdata.com is the latest development snapshot software, folio-stable.aws.indexdata.com is the latest released software that passes integration testing, and folio-demo.aws.indexdata.com is an instance of folio-stable that the product owners have asked us to preserve as a demo site. Currently the folio-demo system has released software from the sprint review before last (sprints 18-19).

I can work with Matt to get Requests ready for release this week, that's fine. If you want to wait until that happens to mint folio-demo, that makes some sense. Just let me know. Thanks!

Comment by Cate Boerema (Inactive) [ 11/Sep/17 ]

I don't have any need for folio-demo if I have folio-stable (since they are essentially the same thing, as I understand it). So, from my (perhaps limited) perspective, there's no urgency to updating folio-demo. Thanks!

Comment by John Malconian [ 11/Sep/17 ]

The main benefit of 'folio-demo' in addition to 'folio-stable' is just to have another copy of FOLIO 'stable' running that can be used for non-engineering demo purposes.

Comment by Wayne Schneider [ 12/Sep/17 ]

Cate Boerema, Charlotte Whitt – unless you have any more feedback on folio-stable, I will install the current system that is "folio-stable" as "folio-demo" (just to have something more up-to-date) and close this issue. We can add in requests when they are ready as released software. Thanks!

Comment by Cate Boerema (Inactive) [ 13/Sep/17 ]

It's okay by me

Comment by Wayne Schneider [ 14/Sep/17 ]

Demo installed.

Generated at Thu Feb 08 23:08:34 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.