Back-end: Fix the CI builds #324
Comments
|
Estimated time: 1 hour |
OrAbramovich
added a commit
that referenced
this issue
Apr 24, 2018
Looks there is a new and unnecessary dependency - deasync so I removed it. #324
OrAbramovich
added a commit
that referenced
this issue
Apr 24, 2018
Additional removals of same redundant dependency leftovers (from package-lock.json) that might cause the failures. #324
OrAbramovich
added a commit
that referenced
this issue
Apr 24, 2018
Reverted previous changes since it didn't help. Tried to re-add it. #324
OrAbramovich
added a commit
that referenced
this issue
Apr 24, 2018
Defined Travis to work with node 9 since I notices that it started to use node 10. #324
Open
|
Actual time: 1 hour. |
|
The reason: TravisCI started to use node js version 10 and one of our dependencies can't be installed on top of it so I configured the CI to build with node js version 9. @chananbental - it's something that you added - deasync - what is it? Is there an alternative that can wotk with node 10? Anyway - TravisCI is back to life (with version 9) and re-builds the project on every commit. Done. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For some reason the Travis-CI build started to fail during the npm install phase. Understand why & resolve! We must have a continuous integration. It's top priority.
The text was updated successfully, but these errors were encountered: