[FOLIO-3085] Honeysuckle (q3-2020) release build fails Created: 22/Mar/21 Updated: 23/Mar/21 Resolved: 23/Mar/21 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | TBD |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||||||||||
| Sprint: | DevOps Sprint 110 | ||||||||||||||||||||
| Development Team: | FOLIO DevOps | ||||||||||||||||||||
| Description |
|
The build now fails pulling module descriptors from the okapi registry because the registry is okapi 4.7.x and the release specifies Okapi version 4.4.2. These versions are incompatible. The q3-2020 release branch of platform-complete and platform-core should be updated with Okapi 4.7.2 to resolve this. |
| Comments |
| Comment by Wayne Schneider [ 22/Mar/21 ] |
|
This also affects the single-server install guide, which is heavily used by new FOLIO SysOps. |
| Comment by Adam Dickmeiss [ 23/Mar/21 ] |
|
|
| Comment by Wayne Schneider [ 23/Mar/21 ] |
|
Adam Dickmeiss we asked for (and received) permission to include Okapi v4.7.2 as part of Honeysuckle. Is backporting still necessary? Jakub Skoczen John Malconian |
| Comment by Adam Dickmeiss [ 23/Mar/21 ] |
|
The problem will resurface when Okapi 4.8.0 comes if that has new features for ModuleDescriptors.. So in any case
|
| Comment by John Malconian [ 23/Mar/21 ] |
|
Updated the honeysuckle release build with Okapi 4.7.2. |
| Comment by David Crossley [ 23/Mar/21 ] |
|
Updated the folio-install single-server guide. |