How to deal with agen/puppeteer/chromium in CI about percy-cypress HOT 8 CLOSED

Hey @MatthD! How are you running percy exec? Are you using npx?

from percy-cypress.

Hi @Robdel12 I am using this script in my package.json for ci "test-functional-ci": "percy exec -- cypress run"

from percy-cypress.

Ah, gotcha. That makes sense. We use the latest version of Puppeteer which will download the version of chromium it needs. If you have chromium preinstalled on the CI image it might be worth locking puppeteer in your project to the same version installed on CI image.

We use 1.13 or greater: https://github.com/percy/percy-agent/blob/master/package.json#L36

Wanted to ask, is this causing issues for you or are you looking to save time and not download chromium?

from percy-cypress.

Oh yeah did not say, it's for saving time because of the downloading ;)

from percy-cypress.

@MatthD how did you solve this?

from percy-cypress.

Hum in fact I was not able to deal with that so just remove chrome from my docker image to have a smaller size et not to download it twice uselessly

from percy-cypress.

FWIW, we won't be moving away from Puppeteer any time soon. You might be able to provide env vars in CI that skips the Puppeteer download and then supply your own Chrome executable path: https://github.com/GoogleChrome/puppeteer/blob/master/docs/api.md#environment-variables

Worth calling out their warning here too:

BEWARE: Puppeteer is only guaranteed to work with the bundled Chromium, use at your own risk.

I'm not sure if that will work, but its worth a shot if you would like to stop installing Chrome that's bundled with Puppeteer.

from percy-cypress.

Hey y'all! Wanted to come back to this and drop a doc for how to skip downloading Chrome if you know the path to an existing Chrome browser on the system: https://docs.percy.io/docs/skipping-puppeteer-chromium-download

from percy-cypress.