Commit graph

23 commits

Author SHA1 Message Date
Bruno Windels
45d1ec8825 set chrome path for travis CI explicitly
karma seems to be giving priority to a location where an old version is installed.
2019-02-28 13:18:21 +01:00
David Baker
1dfaf70562
Revert "Revert "Run lint on travis builds and use modern node versions"" 2018-11-22 18:25:55 +00:00
David Baker
f701e2601a
Revert "Run lint on travis builds and use modern node versions" 2018-11-22 18:17:09 +00:00
David Baker
03587abff1
Update .travis.yml
Remove node 6
2018-11-22 17:54:02 +00:00
Travis Ralston
1fea7c022e Fix order of operations for npm install on Travis CI 2018-10-26 20:44:14 -06:00
Aaron Raimist
c470e2dcfb
Actually I'll just fix the errors myself and get rid of lintwithexclusions
I seemingly need babel-eslint version 8 for VectorHomePage.js but might as well just upgrade to version 10

Signed-off-by: Aaron Raimist <aaron@raim.ist>
2018-10-19 21:04:55 -05:00
Aaron Raimist
fe11ae73db
Run lintwithexclusions on travis builds
Signed-off-by: Aaron Raimist <aaron@raim.ist>
2018-10-19 20:59:07 -05:00
Aaron Raimist
6abd1de8b8
eslint --fix on src/
Signed-off-by: Aaron Raimist <aaron@raim.ist>
2018-10-19 20:59:06 -05:00
lukebarnard
4504ff954a Add sudo: required to travis config 2018-01-19 10:10:13 +00:00
Richard van der Hoff
b375c71a28 fix comments on node versions 2017-07-11 13:23:15 +01:00
Richard van der Hoff
cfe9e762ad Use trusty dist 2017-07-05 10:01:13 +01:00
Richard van der Hoff
9969d6095d Remove phantomjs; add chrome 2017-07-05 09:43:40 +01:00
Michael Telatynski
39ff11fe82 preinstall phantomjs to try get rid of boom error 2017-07-03 18:13:56 +01:00
David Baker
19f9900b55 Merge pull request #4147 from vector-im/rav/fetch_deps_tweaks
Various tweaks to fetch-develop-deps
2017-06-01 18:48:43 +01:00
Richard van der Hoff
81c0c7bd4f Various tweaks to fetch-develop-deps
* tell git to checkout the right branch, rather than cloning and then changing.
* clone with depth 1 under travis, to save time.
* less pushd/popd, which print out confusing text - use `cd` in a subshell
  instead. (and just avoid it where possible).
* add some markers to the output to let travis roll it up.
2017-06-01 18:18:46 +01:00
Richard van der Hoff
71aed70d4b Don't try to build with node 6.0
because it has broken npm
2017-06-01 17:55:52 +01:00
Richard van der Hoff
33b95d4965 Standardise on node v6/v7 2017-05-30 15:53:21 +01:00
David Baker
b3b44dd99e Use fetch dep script for travis 2017-05-17 18:20:25 +01:00
Richard van der Hoff
3404521d5d Fix jenkins build
Do `npm install` on js-sdk rather than `npm run build`, which will hopefully
mean that `browserify` gets installed before we try to run it.

The README says we should use `npm install` for the react-sdk too, so let's do
that, and bring the travis and jenkins builds into sync with the README.
2017-02-01 16:11:11 +00:00
David Baker
0d05e607f0 install js-sdk in travis too 2017-01-12 17:24:28 +00:00
Richard van der Hoff
ebad3da6dd Use node v6 for travis 2016-08-25 14:26:56 +01:00
Richard van der Hoff
d87cf6c02b Transpile the react-sdk before running travis tests 2016-08-25 12:12:20 +01:00
Richard van der Hoff
0c99c5563f Add .travis.yml 2016-08-25 11:56:49 +01:00