[FOLIO-3339] Testing Environment Build Failure Created: 10/Nov/21  Updated: 10/Nov/21  Resolved: 10/Nov/21

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

Type: Bug Priority: TBD
Reporter: Marc Johnson Assignee: Wayne Schneider
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: DevOps Sprint 127
Development Team: FOLIO DevOps

 Description   

Last night's folio-testing-backend build failed.

A rebuild (trigger by me) demonstrated that it is not a transient issue.

The error reported in the logs relates to mod-data-export.

Missing dependency: mod-data-export-4.3.0-SNAPSHOT.280 requires search: 0.6

This is strange because the latest version of mod-seach provides `search 0.7`



 Comments   
Comment by Marc Johnson [ 10/Nov/21 ]

Wayne Schneider John Malconian David Crossley

Could this be caused by the folio-testing build having a fixed order for module enablement and mod-search being enabled after mod-data-export?

That dependency was only introduced yesterday, which would explain the timing and why this only seems to effect the testing environment.

Comment by Wayne Schneider [ 10/Nov/21 ]

Regarding interface version dependencies, the Okapi guide says:

If a module requires an interface 3.2, it will accept:

3.2 – Same version
3.4 – Higher minor version, compatible interfaces

So search 0.7 would be accepted for a requirement of search 0.6

Comment by Wayne Schneider [ 10/Nov/21 ]

As suspected, mod-search needed to be moved in the testing variables file in folio-ansible.

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