Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
29015
dad6dd94 Added slim Chromium-only Playwright runner image for E2E CI no ref - the E2E suite runs exclusively on Chromium (e2e/playwright.config.mjs has no Firefox/WebKit projects), but every E2E shard pulls the upstream mcr.microsoft.com/playwright image which ships all three browser engines - publishes ghcr.io/tryghost/ghost-e2e-runner:v<version> from a dedicated, rarely-triggered workflow instead of ci.yml: the image only changes on a Playwright version or Dockerfile bump and shares no layers with the Ghost build, so there is no buildx-cache reason to co-locate it with job_build_artifacts - Chromium-only + glibc Debian-slim base cuts the compressed pull from ~880MB (MCR) to ~500MB per shard (~4.5GB less per CI run), served from in-network GHCR - kept on glibc (not Alpine/musl): Playwright browser builds are glibc-only, and Alpine would force a system Chromium and break the Chromium<->Playwright version lock - consumers fall back to the upstream Playwright image when the matching runner tag is unavailable (version-bump lag, forks without GHCR, offline), so CI stays green and only loses the speedup until the runner workflow publishes the tag
by Austin Bur...
Succeeded
29015
c27a75b3 Added slim Chromium-only Playwright runner image for E2E CI no ref - the E2E suite runs exclusively on Chromium (e2e/playwright.config.mjs has no Firefox/WebKit projects), but every E2E shard pulls the upstream mcr.microsoft.com/playwright image which ships all three browser engines - publishes ghcr.io/tryghost/ghost-e2e-runner:v<version> from a dedicated, rarely-triggered workflow instead of ci.yml: the image only changes on a Playwright version or Dockerfile bump and shares no layers with the Ghost build, so there is no buildx-cache reason to co-locate it with job_build_artifacts - Chromium-only + glibc Debian-slim base cuts the compressed pull from ~880MB (MCR) to ~500MB per shard (~4.5GB less per CI run), served from in-network GHCR - kept on glibc (not Alpine/musl): Playwright browser builds are glibc-only, and Alpine would force a system Chromium and break the Chromium<->Playwright version lock - consumers fall back to the upstream Playwright image when the matching runner tag is unavailable (version-bump lag, forks without GHCR, offline), so CI stays green and only loses the speedup until the runner workflow publishes the tag
by Austin Bur...
Succeeded
29015
c27a75b3 Added slim Chromium-only Playwright runner image for E2E CI no ref - the E2E suite runs exclusively on Chromium (e2e/playwright.config.mjs has no Firefox/WebKit projects), but every E2E shard pulls the upstream mcr.microsoft.com/playwright image which ships all three browser engines - publishes ghcr.io/tryghost/ghost-e2e-runner:v<version> from a dedicated, rarely-triggered workflow instead of ci.yml: the image only changes on a Playwright version or Dockerfile bump and shares no layers with the Ghost build, so there is no buildx-cache reason to co-locate it with job_build_artifacts - Chromium-only + glibc Debian-slim base cuts the compressed pull from ~880MB (MCR) to ~500MB per shard (~4.5GB less per CI run), served from in-network GHCR - kept on glibc (not Alpine/musl): Playwright browser builds are glibc-only, and Alpine would force a system Chromium and break the Chromium<->Playwright version lock - consumers fall back to the upstream Playwright image when the matching runner tag is unavailable (version-bump lag, forks without GHCR, offline), so CI stays green and only loses the speedup until the runner workflow publishes the tag
by Austin Bur...
Succeeded
29015
c27a75b3 Added slim Chromium-only Playwright runner image for E2E CI no ref - the E2E suite runs exclusively on Chromium (e2e/playwright.config.mjs has no Firefox/WebKit projects), but every E2E shard pulls the upstream mcr.microsoft.com/playwright image which ships all three browser engines - publishes ghcr.io/tryghost/ghost-e2e-runner:v<version> from a dedicated, rarely-triggered workflow instead of ci.yml: the image only changes on a Playwright version or Dockerfile bump and shares no layers with the Ghost build, so there is no buildx-cache reason to co-locate it with job_build_artifacts - Chromium-only + glibc Debian-slim base cuts the compressed pull from ~880MB (MCR) to ~500MB per shard (~4.5GB less per CI run), served from in-network GHCR - kept on glibc (not Alpine/musl): Playwright browser builds are glibc-only, and Alpine would force a system Chromium and break the Chromium<->Playwright version lock - consumers fall back to the upstream Playwright image when the matching runner tag is unavailable (version-bump lag, forks without GHCR, offline), so CI stays green and only loses the speedup until the runner workflow publishes the tag
by Austin Bur...
Succeeded
29015
304a44ed Added slim Chromium-only Playwright runner image for E2E CI no ref - the E2E suite runs exclusively on Chromium (e2e/playwright.config.mjs has no Firefox/WebKit projects), but every E2E shard pulls the upstream mcr.microsoft.com/playwright image which ships all three browser engines - publishes ghcr.io/tryghost/ghost-e2e-runner:v<version> from a dedicated, rarely-triggered workflow instead of ci.yml: the image only changes on a Playwright version or Dockerfile bump and shares no layers with the Ghost build, so there is no buildx-cache reason to co-locate it with job_build_artifacts - Chromium-only + glibc Debian-slim base cuts the compressed pull from ~880MB (MCR) to ~500MB per shard (~4.5GB less per CI run), served from in-network GHCR - kept on glibc (not Alpine/musl): Playwright browser builds are glibc-only, and Alpine would force a system Chromium and break the Chromium<->Playwright version lock - consumers fall back to the upstream Playwright image when the matching runner tag is unavailable (version-bump lag, forks without GHCR, offline), so CI stays green and only loses the speedup until the runner workflow publishes the tag
by Austin Bur...
Succeeded
29015
2f47367b Added slim Chromium-only Playwright runner image for E2E CI no ref - the E2E suite runs exclusively on Chromium (e2e/playwright.config.mjs has no Firefox/WebKit projects), but every E2E shard pulls the upstream mcr.microsoft.com/playwright image which ships all three browser engines - publishes ghcr.io/tryghost/ghost-e2e-runner:v<version> from a dedicated, rarely-triggered workflow instead of ci.yml: the image only changes on a Playwright version or Dockerfile bump and shares no layers with the Ghost build, so there is no buildx-cache reason to co-locate it with job_build_artifacts - Chromium-only + glibc Debian-slim base cuts the compressed pull from ~880MB (MCR) to ~500MB per shard (~4.5GB less per CI run), served from in-network GHCR - kept on glibc (not Alpine/musl): Playwright browser builds are glibc-only, and Alpine would force a system Chromium and break the Chromium<->Playwright version lock - consumers fall back to the upstream Playwright image when the matching runner tag is unavailable (version-bump lag, forks without GHCR, offline), so CI stays green and only loses the speedup until the runner workflow publishes the tag
by Austin Bur...
Succeeded
29015
efda51ee Added slim Chromium-only Playwright runner image for E2E CI no ref - the E2E suite runs exclusively on Chromium (e2e/playwright.config.mjs has no Firefox/WebKit projects), but every E2E shard pulls the upstream mcr.microsoft.com/playwright image which ships all three browser engines - publishes ghcr.io/tryghost/ghost-e2e-runner:v<version> from a dedicated, rarely-triggered workflow instead of ci.yml: the image only changes on a Playwright version or Dockerfile bump and shares no layers with the Ghost build, so there is no buildx-cache reason to co-locate it with job_build_artifacts - Chromium-only + glibc Debian-slim base cuts the compressed pull from ~880MB (MCR) to ~500MB per shard (~4.5GB less per CI run), served from in-network GHCR - kept on glibc (not Alpine/musl): Playwright browser builds are glibc-only, and Alpine would force a system Chromium and break the Chromium<->Playwright version lock - consumers fall back to the upstream Playwright image when the matching runner tag is unavailable (version-bump lag, forks without GHCR, offline), so CI stays green and only loses the speedup until the runner workflow publishes the tag
by Austin Bur...