Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
fix/restore-release-failure-slack-notification
294ad6d4 Merge 56ae4d282c4e959725bead53b8343ae8c6c11cb3 into 1f68d79ed02d61dcc80f2f4248e3ea683b77115c
by Rob Lester
Succeeded
fix/restore-release-failure-slack-notification
37e22b7a Restored Slack notification for release failures When the release flow lived in Ghost-Release it sent an on-call Slack alert on failure (grunt notify-release-failure). After the flow moved into Ghost, release.yml and ci.yml fell back to the generic slack-build "Test failure" message, which doesn't page on-call. Restores an on-call alert at every stage of a release, posting to the existing RELEASE_NOTIFICATION_URL secret. Both stages send the same message — "🚨 Ghost release failed", an @on-call-product page, and a link to the failed run: - release.yml: on a failed prepare/tag run. - ci.yml: a terminal notify_release_failure job that needs the whole publish chain (job_setup -> job_build_artifacts -> job_ghost-cli -> publish_ghost -> create_github_release) and fires on any failure within it. A single aggregator job catches jobs skipped by an upstream failure (e.g. a build failure skips publish_ghost entirely), which a per-job `if: failure()` step cannot. Replaces the per-job slack-build steps. Also gates the create_github_release "is loose!" announcement on the release step itself, so a failed GitHub Release can no longer announce a false success. refs https://github.com/TryGhost/Ghost/pull/26760
by Rob Lester
Succeeded
fix/restore-release-failure-slack-notification
7d0925d5 Merge c6713b763169186891b1960a34b044a1750f2cd8 into 1f68d79ed02d61dcc80f2f4248e3ea683b77115c
by Rob Lester
Succeeded
fix/restore-release-failure-slack-notification
5926af06 Merge 3c11598e1c4bd5fa8d1814e6cfc0122109e832e2 into e68f832d75ec3b66ef110c818e66e1553ceeb9f3
by Rob Lester