devops: remove travis, appveyor, circle for now (#3029)

This commit is contained in:
Pavel Feldman 2020-07-18 10:52:47 -07:00 коммит произвёл GitHub
Родитель b5f9985d3a
Коммит 6199ba28a9
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
5 изменённых файлов: 11 добавлений и 98 удалений

Просмотреть файл

@ -1,11 +0,0 @@
environment:
matrix:
- nodejs_version: "10"
build: off
install:
- ps: Install-Product node $env:nodejs_version
- npm ci
- npm run build
- npm run test

Просмотреть файл

@ -1,25 +0,0 @@
version: 2
jobs:
build:
docker:
- image: mcr.microsoft.com/playwright:dev
steps:
- checkout
- restore_cache:
key: dependency-cache-{{ checksum "browsers.json" }}
- run:
command: npm ci
- run:
command: npm run build
- save_cache:
key: dependency-cache-{{ checksum "browsers.json" }}
paths:
- $HOME/.cache/ms-playwright
- run:
command: |
xvfb-run --auto-servernum npm run test

Просмотреть файл

@ -1,50 +0,0 @@
language: node_js
notifications:
email: false
install:
- npm ci
jobs:
include:
- os: linux
dist: bionic
node_js: '12'
addons:
apt:
packages:
# These are required to run webkit
- libwoff1
- libopus0
- libwebp6
- libwebpdemux2
- libenchant1c2a
- libgudev-1.0-0
- libsecret-1-0
- libhyphen0
- libgdk-pixbuf2.0-0
- libegl1
- libgles2
- libevent-2.1-6
- libnotify4
- libxslt1.1
- libvpx5
# gstreamer and plugins to support video playback in WebKit.
- gstreamer1.0-gl
- gstreamer1.0-plugins-base
- gstreamer1.0-plugins-good
- gstreamer1.0-plugins-bad
# This is required to run chromium
- libgbm1
# this is needed for running headful tests
- xvfb
script:
- npm run build
- xvfb-run --auto-servernum npm run test
- os: osx
osx_image: xcode11.3
node_js: '12'
script:
- npm run build
- npm run test

Просмотреть файл

@ -77,7 +77,6 @@
- [Azure Pipelines](./ci.md#azure-pipelines)
- [Travis CI](./ci.md#travis-ci)
- [CircleCI](./ci.md#circleci)
- [AppVeyor](./ci.md#appveyor)
- [Troubleshooting](./troubleshooting.md)
1. [Selector engines](./selectors.md)
1. [Actionability](./actionability.md)

Просмотреть файл

@ -11,7 +11,6 @@ configurations for common CI providers.
* [Azure Pipelines](#azure-pipelines)
* [Travis CI](#travis-ci)
* [CircleCI](#circleci)
* [AppVeyor](#appveyor)
* [Bitbucket Pipelines](#bitbucket-pipelines)
* [GitLab CI](#gitlab-ci)
- [Caching browsers](#caching-browsers)
@ -94,7 +93,7 @@ steps:
### Travis CI
We run our tests on Travis CI over a Linux agent (Ubuntu 18.04). Use our [Travis configuration](/.travis.yml) to see list of additional dependencies to be installed.
We run our tests on Travis CI over a Linux agent (Ubuntu 18.04).
Suggested configuration
1. [User namespace cloning](http://man7.org/linux/man-pages/man7/user_namespaces.7.html)
@ -113,9 +112,7 @@ dist: bionic
addons:
apt:
packages:
# This is required to run chromium
- libgbm1
# These are required to run webkit
# These are required to run webkit
- libwoff1
- libopus0
- libwebp6
@ -131,7 +128,14 @@ addons:
- libnotify4
- libxslt1.1
- libvpx5
# For headful execution
# gstreamer and plugins to support video playback in WebKit.
- gstreamer1.0-gl
- gstreamer1.0-plugins-base
- gstreamer1.0-plugins-good
- gstreamer1.0-plugins-bad
# This is required to run chromium
- libgbm1
# this is needed for running headful tests
- xvfb
# allow headful tests
@ -145,7 +149,7 @@ before_install:
### CircleCI
We run our tests on CircleCI, with our [pre-built Docker image](docker/README.md). Use our [CircleCI configuration](/.circleci/config.yml) to create your own. Running Playwright smoothly on CircleCI requires the following steps:
We run our tests on CircleCI, with our [pre-built Docker image](docker/README.md). Running Playwright smoothly on CircleCI requires the following steps:
1. Use the pre-built [Docker image](docker/README.md) in your config like so:
@ -166,10 +170,6 @@ We run our tests on CircleCI, with our [pre-built Docker image](docker/README.md
This is likely caused by Jest autodetecting the number of processes on the entire machine (`36`) rather than the number allowed to your container (`2`). To fix this, set `jest --maxWorkers=2` in your test command.
### AppVeyor
We run our tests on Windows agents in AppVeyor. Use our [AppVeyor configuration](/.appveyor.yml) to create your own.
### Bitbucket Pipelines
Bitbucket Pipelines can use public [Docker images as build environments](https://confluence.atlassian.com/bitbucket/use-docker-images-as-build-environments-792298897.html). To run Playwright tests on Bitbucket, use our public Docker image ([see Dockerfile](docker/README.md)).