[FOLIO-747] retain yarn.lock and okapi install.json file from a CI build Created: 26/Jul/17 Updated: 15/Jan/19 Resolved: 02/Aug/17 |
|
| Status: | Open |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | Jakub Skoczen | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, core, sprint19, sprint34 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 2 hours, 45 minutes | ||
| Original estimate: | Not Specified | ||
| Sprint: | |
| Development Team: | Core: Platform |
| Description |
|
For folio-testing, so that developers can repeat the exact same build on their development machine. Other ideas for repeatable builds are welcome. |
| Comments |
| Comment by Wayne Schneider [ 01/Aug/17 ] |
|
The yarn.lock file for any particular CI Vagrant build is available on the Vagrant box at /etc/folio/stripes/yarn.lock. It should also be available in the same location on the EC2 build. Should we be looking at a way to make it more accessible? |
| Comment by Wayne Schneider [ 02/Aug/17 ] |
|
The yarn.lock file is now available on the Stripes container at /yarn.lock. |
| Comment by Wayne Schneider [ 29/Mar/18 ] |
|
The install.json file will be available on the Stripes container at /install.json for snapshot builds (AWS and Vagrant). |