[FOLIO-401] Integrate Stripes components into CI/Jenkins Created: 05/Dec/16 Updated: 12/Nov/18 Resolved: 10/Jan/17 |
|
| Status: | Closed |
| Project: | FOLIO |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None |
| Type: | Task | Priority: | P3 |
| Reporter: | John Malconian | Assignee: | John Malconian |
| Resolution: | Done | Votes: | 0 |
| Labels: | sprint4, sprint5, sprint6 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | 1 day, 1 hour | ||
| Original estimate: | Not Specified | ||
| Issue links: |
|
||||||||
| Sprint: | |||||||||
| Description |
|
The various core Stripes components need to be added to the Jenkin's automated build environment. |
| Comments |
| Comment by John Malconian [ 21/Dec/16 ] |
|
The core Stripes projects (components, loader, and connect) have been added to Jenkins. After discussion with Jason, I've also set up a separate NPM CI registry from the main FOLIO NPM registry to publish NPM artifacts until we settle on a NPM versioning scheme. The NPM CI registry is at https://repository.folio.org/repository/npm-folioci/ |
| Comment by Jakub Skoczen [ 09/Jan/17 ] |
|
John can we resolve this? |
| Comment by Jakub Skoczen [ 10/Jan/17 ] |
|
John, I am assuming this is complete, for any additional work let's file a new issues, for specific components. |