forked from GoogleChrome/lighthouse
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.travis.yml
56 lines (56 loc) · 1.58 KB
/
.travis.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
sudo: required
language: node_js
branches:
only:
- master
matrix:
include:
- node_js: "8"
- node_js: "9"
if: head_branch IS blank AND branch = master
dist: trusty
cache:
yarn: true
directories:
- node_modules
- lantern-data
- lighthouse-extension/node_modules
- lighthouse-viewer/node_modules
- /home/travis/.rvm/gems/
install:
# if our e2e tests fail in the future it might be that we are not compatible
# with the latest puppeteer api so we probably need to run on chromimum
# @see https://github.com/GoogleChrome/lighthouse/pull/4640/files#r171425004
- export PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=1
- yarn
# travis can't handle the parallel install (without caches)
- yarn run install-all:task:windows
before_script:
- export DISPLAY=:99.0
# see comment above about puppeteer
- export CHROME_PATH="$(which google-chrome-stable)"
- sh -e /etc/init.d/xvfb start
- yarn build-all
script:
- yarn bundlesize
- yarn lint
- yarn unit:silentcoverage
- yarn type-check
- yarn diff:sample-json
- yarn smoke:silentcoverage
- yarn test-extension
- yarn test-viewer
- yarn test-lantern
# _JAVA_OPTIONS is breaking parsing of compiler output. See #3338.
- unset _JAVA_OPTIONS
# FIXME(paulirish): re-enable after a roll of LH->CDT
# - yarn compile-devtools
before_cache:
# the `yarn compile-devtools` task adds these to node_modules, which slows down caching
- rm -rf ./node_modules/temp-devtoolsfrontend/
- rm -rf ./node_modules/temp-devtoolsprotocol/
after_success:
- yarn coveralls
- yarn codecov
addons:
chrome: stable