github/puppeteer
0
0
Fork 0
mirror of https://github.com/puppeteer/puppeteer synced 2024-06-14 14:02:48 +00:00
Code Issues Packages Projects Releases Wiki Activity
35d5ba5830
puppeteer/.cirrus.yml

48 lines
1.6 KiB
YAML
Raw Normal View History

chore(CI): add experimental Cirrus CI (#2181) This patch adds experimental support for Cirrus CI builds. Cirrus CI has both Windows and Linux, uses google cloud and runs builds in Docker containers. This seems to be a promising combination for our needs.
2018-03-13 15:06:40 +00:00
env:
DISPLAY: :99.0
chore: introduce initial version of flakiness dashboard (#4781) This patch introduces a dashboard that records test results and uploads them to https://github.com/aslushnikov/puppeteer-flakiness-dashboard Since many bots might push results in parallel, each bot pushes results to its own git branch. FlakinessDashboard also generates a simple README.md with a flakiness summary. If this proves to be not enough, we can build a website that fetches flakiness data and renders it nicely.
2019-08-01 05:23:50 +00:00
FLAKINESS_DASHBOARD_PASSWORD: ENCRYPTED[b3e207db5d153b543f219d3c3b9123d8321834b783b9e45ac7d380e026ab3a56398bde51b521ac5859e7e45cb95d0992]
FLAKINESS_DASHBOARD_NAME: Cirrus ${CIRRUS_TASK_NAME}
chore(flakiness): Flakiness Dashboard fixes (#4788) - fix `FLAKINESS_DASHBOARD_BUILD_URL` to point to a task instead of a build - do not pretty-print `dashboard.json` when serializing flakiness results - filter out 'COVERAGE' test(s) so that they don't add up to `dashboard.json` payload. These are useless - validate certain important options of flakiness dashboard - more logging to STDOUT to actually say which repo and what branch is getting used - enhance commit message with a build URL - use a more compact format for JSON. For 100 runs of 700 tests it yields 21MB json instead of 23MB. - bump default builds number to 100
2019-08-01 23:09:02 +00:00
FLAKINESS_DASHBOARD_BUILD_URL: https://cirrus-ci.com/task/${CIRRUS_TASK_ID}
chore(CI): add experimental Cirrus CI (#2181) This patch adds experimental support for Cirrus CI builds. Cirrus CI has both Windows and Linux, uses google cloud and runs builds in Docker containers. This seems to be a promising combination for our needs.
2018-03-13 15:06:40 +00:00
task:
matrix:
chore(ci): add Puppeteer-Firefox to CI (#3932) This patch adds Puppeteer-Firefox bot running on Linux+Node8 on Cirrus CI. References #3889
2019-02-06 22:28:02 +00:00
- name: Chromium (node8 + linux)
chore(CI): add experimental Cirrus CI (#2181) This patch adds experimental support for Cirrus CI builds. Cirrus CI has both Windows and Linux, uses google cloud and runs builds in Docker containers. This seems to be a promising combination for our needs.
2018-03-13 15:06:40 +00:00
container:
chore(ci): move all CI from Node7 to Node8 (#2938) Node 8 is the current LTS. We should use it by default on all our CIs.
2018-07-26 23:27:11 +00:00
dockerfile: .ci/node8/Dockerfile.linux
chore(ci): add Node10 and Node12 to Cirrus (#4699)
2019-07-14 06:22:02 +00:00
- name: Chromium (node10 + linux)
container:
dockerfile: .ci/node10/Dockerfile.linux
- name: Chromium (node12 + linux)
container:
dockerfile: .ci/node12/Dockerfile.linux
xvfb_start_background_script: Xvfb :99 -ac -screen 0 1024x768x24
chore(CI): add experimental Cirrus CI (#2181) This patch adds experimental support for Cirrus CI builds. Cirrus CI has both Windows and Linux, uses google cloud and runs builds in Docker containers. This seems to be a promising combination for our needs.
2018-03-13 15:06:40 +00:00
install_script: npm install --unsafe-perm
lint_script: npm run lint
coverage_script: npm run coverage
test_doclint_script: npm run test-doclint
chore(types): generate our own d.ts file from api.md (#3744) Generate `//index.d.ts` file with precise typescript definitions for all of the Puppeteer API.
2019-01-28 23:12:45 +00:00
test_types_script: npm run test-types
chore(ci): Configure OSX on Cirrus CI (#2774) Cirrus CI recently started supporting Mac OS builds. This PR adds a CI task to test Puppeteer on MacOS. It uses Node 8 since only [Node 6 and Node 8 are LTS](https://github.com/nodejs/Release#release-schedule) so `brew` only has receipts for those two TLS versions besides the latest one.
2018-06-19 20:03:30 +00:00
chore(ci): add Puppeteer-Firefox to CI (#3932) This patch adds Puppeteer-Firefox bot running on Linux+Node8 on Cirrus CI. References #3889
2019-02-06 22:28:02 +00:00
task:
matrix:
feat(launcher): add option to run Puppeteer with different browsers (#5137) * feat: Set which browser to launch via PUPPETEER_PRODUCT This change introduces a PUPPETEER_PRODUCT environment variable as a first step toward using Puppeteer with many different browsers. Setting PUPPETEER_PRODUCT=firefox, for example, enables Firefox-specific Launcher settings. The state is also exposed as `puppeteer.product` in the API to support adding other product-specific behaviour as needed. The bulk of the change is a refactoring in Launcher to decouple generic browser start-up from product-specific configuration. Respecting the puppeteer-core restriction for PUPPETEER_ environment variables, lazily instantiate the Launcher based on a `product` Puppeteer.launch option, if available. * test: Distinguish Juggler unit tests from Firefox The funit script is renamed to fjunit (j for Juggler, which is used only by the experimental puppeteer-firefox package. In contrast, the funit script now refers to running Puppeteer unit tests against the main puppeteer package with Firefox. To do so with Firefox Nightly, run: `BINARY=path/to/firefox npm run funit` A number of changes in this patch make it easier to run Puppeteer unit tests in Mozilla's CI.
2019-11-26 09:23:19 +00:00
- name: Firefox Juggler (node8 + linux)
chore(ci): add Puppeteer-Firefox to CI (#3932) This patch adds Puppeteer-Firefox bot running on Linux+Node8 on Cirrus CI. References #3889
2019-02-06 22:28:02 +00:00
container:
dockerfile: .ci/node8/Dockerfile.linux
xvfb_start_background_script: Xvfb :99 -ac -screen 0 1024x768x24
install_script: npm install --unsafe-perm && cd experimental/puppeteer-firefox && npm install --unsafe-perm
feat(launcher): add option to run Puppeteer with different browsers (#5137) * feat: Set which browser to launch via PUPPETEER_PRODUCT This change introduces a PUPPETEER_PRODUCT environment variable as a first step toward using Puppeteer with many different browsers. Setting PUPPETEER_PRODUCT=firefox, for example, enables Firefox-specific Launcher settings. The state is also exposed as `puppeteer.product` in the API to support adding other product-specific behaviour as needed. The bulk of the change is a refactoring in Launcher to decouple generic browser start-up from product-specific configuration. Respecting the puppeteer-core restriction for PUPPETEER_ environment variables, lazily instantiate the Launcher based on a `product` Puppeteer.launch option, if available. * test: Distinguish Juggler unit tests from Firefox The funit script is renamed to fjunit (j for Juggler, which is used only by the experimental puppeteer-firefox package. In contrast, the funit script now refers to running Puppeteer unit tests against the main puppeteer package with Firefox. To do so with Firefox Nightly, run: `BINARY=path/to/firefox npm run funit` A number of changes in this patch make it easier to run Puppeteer unit tests in Mozilla's CI.
2019-11-26 09:23:19 +00:00
test_script: npm run fjunit
chore(ci): add Puppeteer-Firefox to CI (#3932) This patch adds Puppeteer-Firefox bot running on Linux+Node8 on Cirrus CI. References #3889
2019-02-06 22:28:02 +00:00
chore(ci): Configure OSX on Cirrus CI (#2774) Cirrus CI recently started supporting Mac OS builds. This PR adds a CI task to test Puppeteer on MacOS. It uses Node 8 since only [Node 6 and Node 8 are LTS](https://github.com/nodejs/Release#release-schedule) so `brew` only has receipts for those two TLS versions besides the latest one.
2018-06-19 20:03:30 +00:00
task:
osx_instance:
image: high-sierra-base
chore(ci): add Puppeteer-Firefox to CI (#3932) This patch adds Puppeteer-Firefox bot running on Linux+Node8 on Cirrus CI. References #3889
2019-02-06 22:28:02 +00:00
name: Chromium (node8 + macOS)
chore(ci): disable brew auto-update (#2861)
2018-07-10 02:23:51 +00:00
env:
HOMEBREW_NO_AUTO_UPDATE: 1
chore(ci): Configure OSX on Cirrus CI (#2774) Cirrus CI recently started supporting Mac OS builds. This PR adds a CI task to test Puppeteer on MacOS. It uses Node 8 since only [Node 6 and Node 8 are LTS](https://github.com/nodejs/Release#release-schedule) so `brew` only has receipts for those two TLS versions besides the latest one.
2018-06-19 20:03:30 +00:00
node_install_script:
- brew install node@8
- brew link --force node@8
install_script: npm install --unsafe-perm
lint_script: npm run lint
coverage_script: npm run coverage
test_doclint_script: npm run test-doclint
chore(types): generate our own d.ts file from api.md (#3744) Generate `//index.d.ts` file with precise typescript definitions for all of the Puppeteer API.
2019-01-28 23:12:45 +00:00
test_types_script: npm run test-types
Reference in New Issue Copy Permalink