puppeteer/.travis.yml

language: node_js
os: linux
dist: trusty
addons:
  apt:
    packages:
      # This is required to run new chrome on old trusty
      - libnss3
notifications:
  email: false
cache:
  directories:
    - node_modules
jobs:
  include:
    - os: "windows"
      node_js: "10.19.0"
      env:
        - CHROMIUM=true
      before_install:
        # populate .local-firefox for launcher tests
        - PUPPETEER_PRODUCT=firefox npm install
      script:
        - ls .local-chromium .local-firefox
        - npm run tsc
        - travis_retry npm run unit
    - node_js: "10.19.0"
      dist: trusty
      env:
        - CHROMIUM=true
      before_install:
        - "export DISPLAY=:99.0"
        - "sh -e /etc/init.d/xvfb start"
        # populate .local-firefox for launcher tests
        - PUPPETEER_PRODUCT=firefox npm install
      script: ./travis/chromium.sh
    - node_js: "10.19.0"
      dist: trusty
      env:
        - FIREFOX=true
      before_install:
        - "export DISPLAY=:99.0"
        - "sh -e /etc/init.d/xvfb start"
        # install step will add .local-chromium for launcher tests
        - PUPPETEER_PRODUCT=firefox npm install
      script:
        -  "npm run funit"
Add travis config (#29) This patch: - adds travis - adds eslint as required in devdeps - cleans up travis yml 2017-06-21 00:04:24 +00:00			`language: node_js`
chore: update CI to run Travis + Linux + Chromium (#5583) Our CI build has been incredibly flaky across all three of our current CIs: * Appveyor: Chromium + Windows * Travis: Firefox + Linux, Chromium + Linux * Cirrus: Chromium + Linux, Chromium + Mac Legitimate issues and errors have been missed because it's expected that the CI is red and therefore it's not seen as an issue when a PR's build fails. We should have a build that covers the full combo of browsers and operating systems but it's more important to have a consistent, reliable green build where failures are genuine. So this commit strips our CI back to Chromium on Linux on Travis, and nothing more. Once this is stable we will expand out into more operating systems and bring back Firefox, too. 2020-04-08 09:38:07 +00:00			`os: linux`
Add travis config (#29) This patch: - adds travis - adds eslint as required in devdeps - cleans up travis yml 2017-06-21 00:04:24 +00:00			`dist: trusty`
Update libssn3 via .travis.yml References #33. 2017-06-21 03:48:35 +00:00			`addons:`
			`apt:`
			`packages:`
			`# This is required to run new chrome on old trusty`
			`- libnss3`
chore(CI): disable email notifications (#2412) 2018-04-19 20:27:37 +00:00			`notifications:`
			`email: false`
Add travis config (#29) This patch: - adds travis - adds eslint as required in devdeps - cleans up travis yml 2017-06-21 00:04:24 +00:00			`cache:`
			`directories:`
			`- node_modules`
Node 6 support (#484) This patch: - introduces a transpiler which substitutes async/await logic with generators. - starts using the transpiler to generate a node6-compatible version of puppeteer - introduces a runtime-check to decide which version of code to use Fixes #316. 2017-08-24 19:20:05 +00:00			`jobs:`
			`include:`
chore(ci): re-enable tests on Windows (#5637) * chore: Add Windows to Travis This commit runs the unit tests on Windows. There are two tests failing on Windows that we skip. I spoke to Mathias B and we agreed to defer debugging this for now in favour of getting tests running on Windows. But we didn't want to ignore it forever, hence giving the test a date at which it will start to fail. 2020-04-17 13:27:50 +00:00			`- os: "windows"`
			`node_js: "10.19.0"`
			`env:`
			`- CHROMIUM=true`
			`before_install:`
			`# populate .local-firefox for launcher tests`
			`- PUPPETEER_PRODUCT=firefox npm install`
			`script:`
			`- ls .local-chromium .local-firefox`
			`- npm run tsc`
chore: migrate `src/USKeyboardLayout` to typescript (#5695) * chore: migrate `src/USKeyboardLayout` to typescript Don't think we need to expose the interface type for the keycodes so I've left it local for now. * retry windows unit tests 2020-04-21 09:21:45 +00:00			`- travis_retry npm run unit`
chore: update CI to run Travis + Linux + Chromium (#5583) Our CI build has been incredibly flaky across all three of our current CIs: * Appveyor: Chromium + Windows * Travis: Firefox + Linux, Chromium + Linux * Cirrus: Chromium + Linux, Chromium + Mac Legitimate issues and errors have been missed because it's expected that the CI is red and therefore it's not seen as an issue when a PR's build fails. We should have a build that covers the full combo of browsers and operating systems but it's more important to have a consistent, reliable green build where failures are genuine. So this commit strips our CI back to Chromium on Linux on Travis, and nothing more. Once this is stable we will expand out into more operating systems and bring back Firefox, too. 2020-04-08 09:38:07 +00:00			`- node_js: "10.19.0"`
			`dist: trusty`
chore: run Chromium on Node.js 12 on Travis (#5582) 2020-04-03 11:22:02 +00:00			`env:`
			`- CHROMIUM=true`
chore: update CI to run Travis + Linux + Chromium (#5583) Our CI build has been incredibly flaky across all three of our current CIs: * Appveyor: Chromium + Windows * Travis: Firefox + Linux, Chromium + Linux * Cirrus: Chromium + Linux, Chromium + Mac Legitimate issues and errors have been missed because it's expected that the CI is red and therefore it's not seen as an issue when a PR's build fails. We should have a build that covers the full combo of browsers and operating systems but it's more important to have a consistent, reliable green build where failures are genuine. So this commit strips our CI back to Chromium on Linux on Travis, and nothing more. Once this is stable we will expand out into more operating systems and bring back Firefox, too. 2020-04-08 09:38:07 +00:00			`before_install:`
			`- "export DISPLAY=:99.0"`
			`- "sh -e /etc/init.d/xvfb start"`
fix: set revision based on PUPPETEER_PRODUCT (#5643) 2020-04-15 11:30:42 +00:00			`# populate .local-firefox for launcher tests`
			`- PUPPETEER_PRODUCT=firefox npm install`
chore: update CI to run Travis + Linux + Chromium (#5583) Our CI build has been incredibly flaky across all three of our current CIs: * Appveyor: Chromium + Windows * Travis: Firefox + Linux, Chromium + Linux * Cirrus: Chromium + Linux, Chromium + Mac Legitimate issues and errors have been missed because it's expected that the CI is red and therefore it's not seen as an issue when a PR's build fails. We should have a build that covers the full combo of browsers and operating systems but it's more important to have a consistent, reliable green build where failures are genuine. So this commit strips our CI back to Chromium on Linux on Travis, and nothing more. Once this is stable we will expand out into more operating systems and bring back Firefox, too. 2020-04-08 09:38:07 +00:00			`script: ./travis/chromium.sh`
chore(test): re-enable Firefox testing on CI (#5608) 2020-04-08 10:18:29 +00:00			`- node_js: "10.19.0"`
			`dist: trusty`
			`env:`
			`- FIREFOX=true`
			`before_install:`
			`- "export DISPLAY=:99.0"`
			`- "sh -e /etc/init.d/xvfb start"`
fix: set revision based on PUPPETEER_PRODUCT (#5643) 2020-04-15 11:30:42 +00:00			`# install step will add .local-chromium for launcher tests`
			`- PUPPETEER_PRODUCT=firefox npm install`
chore(test): re-enable Firefox testing on CI (#5608) 2020-04-08 10:18:29 +00:00			`script:`
fix: set revision based on PUPPETEER_PRODUCT (#5643) 2020-04-15 11:30:42 +00:00			`- "npm run funit"`