forked from GoogleChrome/lighthouse
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.travis.yml
54 lines (54 loc) · 1.43 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
sudo: required
language: node_js
branches:
only:
- master
matrix:
include:
- node_js: "10"
- node_js: "12"
if: head_branch IS blank AND branch = master
cache:
yarn: true
directories:
- node_modules
- lantern-data
- /home/travis/.rvm/gems/
install:
# Ensure we have the latest Chrome stable.
- google-chrome-stable --version
# We used to set PUPPETEER_SKIP_CHROMIUM_DOWNLOAD, but we don't want to anymore.
# Explicitly unset b/c environment variables seem to linger in travis.
# see https://github.com/GoogleChrome/lighthouse/pull/9877#discussion_r338389765
- unset PUPPETEER_SKIP_CHROMIUM_DOWNLOAD
- yarn --frozen-lockfile
before_script:
# see comment above about puppeteer
- export CHROME_PATH="$(which google-chrome-stable)"
# Print out the Chrome version so we know what we're working with
- google-chrome-stable --version
- yarn build-all
script:
- yarn bundlesize
- yarn diff:sample-json
- yarn lint
- yarn unit:cicoverage
- yarn type-check
- yarn smoke:cicoverage
- yarn test-clients
- yarn test-viewer
- yarn test-lantern
- yarn test-bundle || yarn test-bundle || yarn test-bundle
- yarn i18n:checks
- yarn dogfood-lhci
- yarn test-docs
before_cache:
# nyc, jest and other projects store files in here. They mess up the travis build cache.
- rm -rf ./node_modules/.cache/
after_success:
- yarn coveralls
- yarn codecov
addons:
chrome: stable
services:
- xvfb