[FOLIO-2193] Snapshot and testing environment builds reports inconsistent login interface expectations Created: 25/Jul/19  Updated: 03/Jun/20  Resolved: 25/Jul/19

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

Type: Bug Priority: P2
Reporter: Marc Johnson Assignee: Viachaslau Khandramai (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:

 Description   

The FOLIO snapshot build reported an inconsistency in expectations for the login interface this morning:

Incompatible version for module mod-users-bl-5.1.0-SNAPSHOT.69 interface login. Need 6.0. Have 5.0/edge-rtac-2.0.2-SNAPSHOT.55/edge-orders-2.1.0-SNAPSHOT.25/edge-patron-3.0.3-SNAPSHOT.40/edge-oai-pmh-2.1.0-SNAPSHOT.26. Incompatible version for module folio_users-2.23.4000728 interface login. Need 6.0. Have 5.0/edge-rtac-2.0.2-SNAPSHOT.55/edge-orders-2.1.0-SNAPSHOT.25/edge-patron-3.0.3-SNAPSHOT.40/edge-oai-pmh-2.1.0-SNAPSHOT.26"

The same issue appears to have affected the [folio-testing build|] as well



 Comments   
Comment by Marc Johnson [ 25/Jul/19 ]

I think this might be related to the last release of edge-orders.

The snapshot build is including build 25 rather than build 26 in the environment, and I think this could be to do with a malformed (it only has two parts) snapshot version set after the release:

<version>2.1-SNAPSHOT</version>

Jakub Skoczen could this confuse Okapi’s ordering of module versions?

Kostyantyn Khodarev I couldn’t find the person who made this change in JIRA from their github username, maybe you can help me identify them, unless it was Kruthi Vuppala using a different username?

Comment by Marc Johnson [ 25/Jul/19 ]

This hypothesis seems to be reinforced by the output from the registry which lists build 25 after 26 (assuming this is listed in ascending version order):

{
  "id" : "edge-orders-1.0.1-SNAPSHOT.18",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-1.0.1-SNAPSHOT.19",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-1.0.1-SNAPSHOT.20",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-1.0.1-SNAPSHOT.21",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-2.0.0",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-2.0.1",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-2.0.2",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-2.1-SNAPSHOT.26",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-2.1.0-SNAPSHOT.22",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-2.1.0-SNAPSHOT.23",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-2.1.0-SNAPSHOT.24",
  "name" : "Acquisitions - Orders Edge API"
}, {
  "id" : "edge-orders-2.1.0-SNAPSHOT.25",
  "name" : "Acquisitions - Orders Edge API"
}

(There is something odd going on here, as the snapshot versions are 2.1.0 both prior to and after formal releases, I wonder if that is because some of the release versions are bug fix versions, yet they have been released from master)

Comment by Viachaslau Khandramai (Inactive) [ 25/Jul/19 ]

Hi Marc Johnson,
I have already updated version edge-orders-2.1-SNAPSHOT to edge-orders-2.1.0-SNAPSHOT.

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