From 16e17e631cc1a602bc193c0dff2f688b2ed2a178 Mon Sep 17 00:00:00 2001 From: Pascal Birchler Date: Tue, 21 May 2019 15:20:24 +0200 Subject: [PATCH] Do not try to download Chromium by default This happens because the wordpress/scripts package depends on Puppeteer, which results in attempts to download Chromium when running `npm install`. Once we use Puppeteer for end-to-end tests that can be run on Travis, we can enable the download again just for that stage. Related: https://github.com/WordPress/gutenberg/pull/15712 --- .travis.yml | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.travis.yml b/.travis.yml index 435c6a71aa6..5d4025146aa 100644 --- a/.travis.yml +++ b/.travis.yml @@ -23,6 +23,8 @@ cache: - $HOME/phpunit-bin - $HOME/deployment-targets +env: PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true + install: - nvm install 8.11.4 && nvm use 8.11.4 - composer install