[FOLIO-3147] Base folio-testing builds on install.json files from platform-complete Created: 06/May/21  Updated: 10/May/23  Resolved: 21/Feb/22

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

Type: Task Priority: TBD
Reporter: John Malconian Assignee: Unassigned
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 160
Development Team: FOLIO DevOps

 Description   

folio-snapshot-based builds use the install.json files in platform-core and platform-complete to determine which versions of modules to deploy and the order in which they can be enabled. folio-testing builds, instead, use a combination of ansible configuration and okapi dependency resolution to determine module versions. Modify the Ansible playbooks which build folio-testing to use the same files to determine the backend module versions to deploy as well as the order in which they are enabled for the tenant so that doesn't need to be defined in an Ansible configuration.



 Comments   
Comment by Jakub Skoczen [ 08/Nov/21 ]

I will ask on the PO channel if we can shut-down folio-tetsting and replace it with another build of folio-snapshot build at 9am ET.

Comment by Marc Johnson [ 10/Nov/21 ]

Jakub Skoczen

I will ask on the PO channel if we can shut-down folio-tetsting and replace it with another build of folio-snapshot build at 9am ET.

What is the intent of having another snapshot like environment rather than directing folks to the existing environment?

The audience for folks who use these environments isn't only the POs. Many of the UI developers rely on these environments for day to day work (e.g. this slack conversation)

Comment by Marc Johnson [ 10/Nov/21 ]

John Malconian Wayne Schneider

folio-testing builds, instead, use a combination of ansible configuration and okapi dependency resolution to determine module versions. Modify the Ansible playbooks which build folio-testing to use the same files to determine the backend module versions to deploy as well as the order in which they are enabled for the tenant so that doesn't need to be defined in an Ansible configuration.

As I understand, one of the primary goals for the testing environment is to get early feedback on the compatibility between head of the mainline module versions (which the snapshot build process deliberately obscures).

How wrong is my understanding of this intent?

If it is somewhat correct, I would think that using the platform complete definitions undermines a primary goal of those builds. Have I misunderstood what is being proposed here?

Comment by Jakub Skoczen [ 21/Feb/22 ]

Deprecated in favour of FOLIO-3419 Closed

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