[FOLIO-2865] Inconsistent build dependencies leaking into folio-snapshot Created: 05/Nov/20 Updated: 10/Nov/20 Resolved: 10/Nov/20 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P2 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | DevOps: Sprint 101 | ||||||||
| Development Team: | FOLIO DevOps | ||||||||
| Description |
|
How did folio-snapshot end up with @folio/circulation v5.0.1000577 in the webpack and in stripes-install.json, but v4.0.1000572 as the actual enabled version in Okapi? |
| Comments |
| Comment by Wayne Schneider [ 05/Nov/20 ] |
|
John Malconian observes:
|
| Comment by John Malconian [ 05/Nov/20 ] |
|
Subsequently, the same behavior is observed when building folio-snapshot. the folio-snapshot build doesn't use the install.json file. It uses stripes-install.json from platform-complete which would have ui-circulation-5.0.1000577 and okapi-install.json (backend modules). So somehow, it appears Okapi downgraded ui-circ to ui-circ-4.0.1000572 when stripes-install.json was posted to the okapi install endpoint. This is consistent to what we observe in the build-platform-complete pipeline. |
| Comment by Jakub Skoczen [ 10/Nov/20 ] |
|
Wayne Schneider will provide a test case for this. Adam Dickmeiss |
| Comment by Wayne Schneider [ 10/Nov/20 ] |
|
Bug report filed as
|