Closed v1v closed 4 years ago
@v1v Is it possible to mirror the chrome download artefacts within our infra? there's an env variable PUPPETEER_DOWNLOAD_HOST
that we can use to point the installation to download chrome from our own mirror instead of the default.
None of these options works
RUN npm set puppeteer_skip_download true \
&& npm set puppeteer_skip_chromium_download true \
&& npm config set puppeteer_skip_download true -g \
&& npm config set puppeteer_skip_chromium_download true -g \
&& PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true npm install
so I will implement a retry for the install
build failed as a consequence of the downstream build, see the below stacktrace:
There was a kind of fix back in the days for the opbeans-frontend:
But it seems the issue still persists. Besides @vigneshshanmugam pointed the env variable might not be the way to fix it. @kuisathaverat suggested to use our well known retry/sleep framework.
I wonder if the above fix is valid though, there is a comment regarding that particular env variable:
@vigneshshanmugam and @jahtalab would you mind to have a look?