[FOLIO-1287] Set up mod-graphql Jenkins to provide mod-inventory-storage Created: 13/Jun/18 Updated: 12/Nov/18 Resolved: 20/Jun/18 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | Continuous Integration |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Mike Taylor | Assignee: | Mike Taylor |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | ci, sprint40 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||||||
| Sprint: | |||||||||||||
| Description |
|
I want to extend the tests of mod-graphql so that they encompass autogenerating a GraphQL schema and resolvers from the RAML and associated JSON files of mod-inventory-storage. For that to work, I need `yarn test` to run in an environment where it has access to a fresh git checkout of that module, including its raml-utils submodule, in a known location. |
| Comments |
| Comment by Mike Taylor [ 13/Jun/18 ] |
|
After discussing with John Malconian, we concluded that it's simpler, rather than messing with Jenkins, to just have yarn test create whatever prerequisites it needs. That is potentially a bit heavyweight, and makes the tests dependent on an available network connection. Then we realised I could just make it only do this if the checkout isn't already there. So that's what I'll do. |
| Comment by Mike Taylor [ 20/Jun/18 ] |
|
Closing as WON'T DO, since
|