[FOLIO-1505] Pull request environment build fails when sample data is out of sync Created: 17/Sep/18 Updated: 18/Jan/19 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Marc Johnson | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | ci, core, sprint47, sprint48 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Core: Platform |
| Description |
|
As discussed here: https://folio-project.slack.com/archives/C210RP0T1/p1536838620000200 Mike Taylor observed that a pull request build for UI users failed: https://jenkins-aws.indexdata.com/blue/organizations/jenkins/folio-org%2Fui-users/detail/PR-503/1/pipeline Summary Pull request builds use folio-snapshot-stable as the basis for the environment created to run the UI regression tests on a pull request. If a backend modules provides sample data (e.g. mod-inventory-storage), the build will fail if there are incompatibilities between the record structure in the version in folio-snapshot and the record structure of the sample data at the head of master. In these circumstances, additional properties are incompatible (as FOLIO schema disallow additional properties). Unfortunately, further information is not available as the pull request build history has been purged from Jenkins. Workaround Disable the tests for pull requests until folio-snapshot-stable is updated to a compatible version. |