8 Commits (b416ecca5c2e0ac1626964cd72065d05581497e0)

Author	SHA1	Message	Date
Kurt Garloff	8f84f2f916	jibri: use storage.googleapis.com location for chromedriver ... This is the place listed on https://googlechromelabs.github.io/chrome-for-testing/ which would seem to be the least likely to silently break. Currently, the edgedl.me.gvt1.com location is broken. Signed-off-by: Kurt Garloff <kurt@garloff.de>	9 months ago
Saúl Ibarra Corretgé	d31e164656	build: simplify detection of the target platform ... It can be done within the container, rather than having to compute it in the Makefile and then pass it as an argument.	10 months ago
Saúl Ibarra Corretgé	603d461179	jibri: adapt to new ChromeDriver zip file structure	1 year ago
Saúl Ibarra Corretgé	a76b1f4b4a	jibri: simplify ChromeDriver download	1 year ago
Saúl Ibarra Corretgé	fd1c308b49	jibri: fix new ChromeDriver API endpoints	1 year ago
Saúl Ibarra Corretgé	2c0a7931b2	jibri: update Chrome to 116 ... Note the URL for the ChromeDriver has changed now.	1 year ago
Saúl Ibarra Corretgé	076dbf7d17	jibri: fix downloading new (>= 109) ChromeDriver	2 years ago
Saúl Ibarra Corretgé	e7533f8639	jibri: simplify Dockerfile ... Slightly reduce layer count by running everything in a single RUN. Also reduce build time by skipping some unneeded apt update / cleanups.	2 years ago
Saúl Ibarra Corretgé	829841e1a4	jibri: add support for arm64 ... Use Debian's Chromium and ChromeDriver instead of Google's. This has the limitation of not being able to control the version we ship, however.	2 years ago
Ben Banfield-Zanin	238a6369e8	jibri: correct chromedriver mismatch ... * jibri: turn on -x so that we can see what is actually executing * jibri: bail out on the build if the actual release doesn't match the major release * jibri: ensure the correct chromedriver gets downloaded when CHROME_RELEASE != latest * jibri: move chrome installation to a separate script	3 years ago