-
Task
-
Resolution: Done
-
Major
-
None
-
None
-
None
-
Service Team-Sprint 27, Service Team-Sprint 28
-
https://github.com/aerogear/aerogear-js-sdk/pull/404, https://github.com/aerogear/voyager-server/pull/197, https://github.com/aerogear/aerogear-integration-tests/pull/16, https://github.com/aerogear/aerogear-integration-tests/pull/10, https://github.com/aerogear/aerogear-unifiedpush-nodejs-client/pull/38, https://github.com/aerogear/aerogear-integration-tests/pull/19
Currently, we are building aerogear projects (js-sdk, voyager-server, ...) inside the integration-tests Jenkins pipeline, but this can generate random issues in the future (example: different versions of node or npm for building a package, ...), in order to avoid these problems is better that each project create a nightly build or a master build of himself, upload it to npm, dockerhub, ... and that the interation-tests pipeline use this builds during the nightly tests.
Projects:
- aerogear-js-sdk (npm packages)
- aerogear-app-metrics (container)
- aerogear-unifiedpush-server (container)
- voyager-server (npm package)
- aerogear-unifiedpush-nodejs-client (npm packages)
Also, add badge with build status to each project.