thunderstrike/puppeteer
thunderstrike/puppeteer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

docs(circleci): Add CircleCI to troubleshooting docs (#4810)

Browse Source 
This came from personal difficulties in running Puppeteer tests on CircleCI. I tried to keep the note as brief as possible, while being helpful for an entire CI platform.
This commit is contained in:
Drew Powers 2019-08-06 19:18:10 -05:00 committed by Andrey Lushnikov
parent dcff850b6f
commit 374177b433
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
docs/troubleshooting.md
View File

@ -7,6 +7,7 @@
* [[recommended] Enable user namespace cloning](#recommended-enable-user-namespace-cloning)
* [[alternative] Setup setuid sandbox](#alternative-setup-setuid-sandbox)
- [Running Puppeteer on Travis CI](#running-puppeteer-on-travis-ci)
- [Running Puppeteer on CircleCI](#running-puppeteer-on-circleci)
- [Running Puppeteer in Docker](#running-puppeteer-in-docker)
* [Running on Alpine](#running-on-alpine)
- [Tips](#tips)
@ -214,6 +215,14 @@ before_install:
- "sh -e /etc/init.d/xvfb start"
```
## Running Puppeteer on CircleCI
CircleCI has a shared [orb](https://circleci.com/orbs/) that can be used to
install missing dependencies:
[threetreeslight/puppeteer](https://circleci.com/orbs/registry/orb/threetreeslight/puppeteer).
You can either use the orb as-is ([docs](https://circleci.com/orbs/)), or
copy parts of that config into your own as-needed.
## Running Puppeteer in Docker