[FOLIO-1590] better interface incompatibility reporting Created: 22/Oct/18 Updated: 18/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Zak Burke | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Core: Platform |
| Description |
DescriptionReporting is inadequate for a build that requests an incompatible collection of interfaces. DetailsWe recently updated a backend-dependency (
Details from the build log for the most recent failure:
FAILED! => {"changed": false, "connection": "close", "content": "Incompatible version for module folio_organization-2.5.1000133 interface locations. Need 3.0. Have 2.1", "content_length": "102", "content_type": "text/plain", "msg": "Status code was 400 and not [200]: HTTP Error 400: Bad Request", "redirected": false, "status": 400, "url": "http://10.36.1.171:9130/_/proxy/tenants/diku/install?simulate=true"}
This is inaccurate – there was never a locations v2.1 interface; it moved from v2.0 to v3.0; service-points moved from v2.0 to v2.1 – but that's somewhat beside the point. When there is an interface incompatibility, it would be helpful to know all the modules requesting the interface in question in order to figure out all the modules whose Okapi dependencies we need to sync. |