[FOLIO-387] Automate demo and backend build for thin-thread development Created: 10/Nov/16  Updated: 12/Nov/18  Resolved: 03/Apr/17

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

Type: Task Priority: P3
Reporter: Mike Taylor Assignee: John Malconian
Resolution: Done Votes: 0
Labels: ci, sprint3
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 3 days, 6 hours Time Spent: 2 days, 45 minutes
Σ Original Estimate: Not Specified Original estimate: Not Specified

Issue links:
Blocks
is blocked by STRIPES-30 UI tests for stripes-connect Closed
is blocked by FOLIO-401 Integrate Stripes components into CI/... Closed
Duplicate
is duplicated by FOLIO-384 Integrate image build into CI workflow Closed
Relates
relates to FOLIO-669 Fully automate builds of "stable" and... Closed
relates to LIBAPP-51 Simple UI control for listing users Closed
Sub-tasks:
Key
Summary
Type
Status
Assignee
FOLIO-383 Write Packer script to build Vagrant ... Sub-task Closed Wayne Schneider  
Sprint:

 Description   

As we complete LIBAPP-51 Closed , and take on further thin-thread development in future sprints, we'll want a way to demo this work without needing to screen-share Jason's laptop. We probably want a complete end-to-end CI system that we can push changes to, and see them appear in a public demo space – whether changes to UI modules, the Stripes code, Okapi or back-end modules.

The urgency of this is not clear, so I am leaving it at P3 for now.



 Comments   
Comment by Mike Taylor [ 10/Nov/16 ]

Assigning to John initially, but not necessarily with the expectation that this will happen as a priority. (Seb, you might want to comment on urgency?)

Comment by Mike Taylor [ 10/Nov/16 ]

Wayne rightly points out that this overlaps with FOLIO-384 Closed . It could even be a dup.

Comment by Jakub Skoczen [ 15/Nov/16 ]

There is urgency in terms of completing the work on LIBAPP-51 Closed , which this is in my mind is an integral part. Wayne Schneider and John Malconian let's discuss this during he backend meeting today.

Comment by John Malconian [ 22/Nov/16 ]

Mike Taylor Jason Skomorowski Wolfram Schneider - Are there Stripes components that are ready to incorporate into Jenkins builds at this point? If so, can you point me to the relevant git repositories? As it stands now, nothing related to Stripes is incorporated into our Jenkins build process.

Comment by Mike Taylor [ 22/Nov/16 ]

There are many parts of Stripes that are working now – both the components of Stripes itself and modules that run under Stripes. The best guide to what exists, and how to make it work, is Running a complete FOLIO system at https://github.com/folio-org/ui-okapi-console/blob/master/doc/running-a-complete-system.md

The key git repos you'll need are

  • stripes-components
  • stripes-connect
  • stripes-core
  • stripes-experiments
  • stripes-loader
  • ui-okapi-console
Comment by John Malconian [ 03/Apr/17 ]

Completed. http://folio-uidemo.aws.indexdata.com is the current location of the demo which is built nightly currently using the tip of master for all backend and frontend components.

Comment by Jakub Skoczen [ 13/Jun/17 ]

John Malconian Wayne Schneider Guys, this issue is linked to in the CI/CD goals document but it's been closed for at least two months and I don't think it delivered on the premise captured in the document. I will create a new issue and link it here (and put in the document)

Comment by Jakub Skoczen [ 13/Jun/17 ]

the link should say "superseded by"

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