[FOLIO-884] Update yarn.lock on folio-testing-platform after CI build Created: 06/Oct/17 Updated: 12/Nov/18 Resolved: 15/Nov/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | Continuous Integration |
| Affects versions: | None |
| Fix versions: | None |
| Type: | New Feature | Priority: | P3 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | ci, sprint24, sprint25, sprint26 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Sprint: |
| Description |
|
If we could update the yarn.lock for folio-testing-platform after each successful stripes-testing build, developers could be sure they are building a platform that matches the folio-testing AWS instance. |
| Comments |
| Comment by Wayne Schneider [ 15/Nov/17 ] |
|
It works better to have no yarn.lock for this platform. Generated yarn.lock for a build made with folio-ansible is available in the nginx (stripes) Docker container as well as in the /etc/folio/stripes directory on the target host. |