I noticed caching the node_modules folder caused problems (build fails) while caching the .npm cache avoided it. I believe it’s because the .npm cache doesn’t store compiled native modules while the node_modules folder does. So when you test different versions of node, as is common in Travis-CI, it will try to load a native module …
One way to inspect the build (not to debug, sorry) is to send the build logs to another server on failure. Here is an example: after_failure – sudo tar -czf /tmp/build-${TRAVIS_BUILD_NUMBER}-logs.tgz your-application-logs/ – scp /tmp/build-${TRAVIS_BUILD_NUMBER}-logs.tgz travis@your-server.com:~/logs You could send them via email, store them on a storage server or whatever. These logs would be useful …
You don’t have 32 lines in your file (probably because you stripped non-essential data out of the example), but the indentation level points to the line with fi. Actually the problem starts earlier and what you want to do is specify the action to take as a multi-line string. You can specify those in YAML …
Have you made sure to install grunt-cli globally on your Travis node? My Travis CI config looks like: language: node_js node_js: – “0.8” before_install: npm install -g grunt-cli install: npm install before_script: grunt build And my package.json: { … “scripts”: { “test”: “grunt test” }, … } I will explain the flow of steps that …
I had met same issue. First I remove ts-node and typescript from package.json. then, npm install ts-node –save-dev npm install typescript -g npm install typescript –save-dev
It is not possible yet to have several languages on travis configuration file. On the other hand, all environments run node.js. The following script does the trick: language: ruby rvm: – 2.0.0 before_script: – npm install karma script: – RAILS_ENV=test bundle exec rake –trace db:migrate test – karma start –single-run –browsers PhantomJS test/karma/config/unit.js Help found …
That is a bug that came with node v11.11. You can downgrade to v11.10 or wait for the fix which facebook has already pushed (jest error in Node version over 11.11). If your problem is TravisCI related then you can set a fixed version which works: node_js: – “11.10.1”
I had the same error: radato$ git submodule update fatal: git upload-pack: not our ref somehash0 fatal: remote error: upload-pack: not our ref somehash0 fatal: Fetched in submodule path ‘dashboard’, but it did not contain somehash0. Direct fetching of that commit failed. So I deinitialized the submodule: radato$ git submodule deinit -f dashboard Cleared directory …
This can (thankfully) be easily solved by modifying the .gitmodules file on-the-fly on Travis, so that the SSH URL is replaced with the public URL, before initializing submodules. To accomplish this, add the following to .travis.yml: # Handle git submodules yourself git: submodules: false # Use sed to replace the SSH URL with the public …