[FOLIO-876] yarn build errors don't prevent a successful CI build Created: 03/Oct/17 Updated: 12/Nov/18 Resolved: 09/Oct/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | Continuous Integration |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Bug | Priority: | P3 |
| Reporter: | Wayne Schneider | Assignee: | Wayne Schneider |
| Resolution: | Done | Votes: | 0 |
| Labels: | ci, sprint23 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 hour, 45 minutes | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
Several times in the last week there have been yarn build errors that don't get captured by the CI stripes build process. This results in an apparently successful build with a broken system. |
| Comments |
| Comment by Wayne Schneider [ 03/Oct/17 ] |
|
The issue is that the webpack build command in stripes-core reports errors, but doesn't actually fail – so pretty much all webpack builds succeed, from the perspective of yarn build. See
|
| Comment by Wayne Schneider [ 04/Oct/17 ] |
|
With the change to stripes-core in
|