From 67d4e2bfa32537e5c2e459b10ce1e14401deee9a Mon Sep 17 00:00:00 2001 From: Callum Gardner <10970827+ctgardner@users.noreply.github.com> Date: Thu, 27 Jun 2024 09:59:42 +1000 Subject: [PATCH] ci: add release notifier to pipeline Configured a Slack message to be sent to Team SRE Foundations when a new release is ready to be published. (Effectively, after every merge into `origin/main`.) This notifier was added to ensure dependency upgrades are actually released, not just merged and forgotten/unreleased. --- .buildkite/pipeline.yaml | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/.buildkite/pipeline.yaml b/.buildkite/pipeline.yaml index 38be2cb..7fc5311 100644 --- a/.buildkite/pipeline.yaml +++ b/.buildkite/pipeline.yaml @@ -1,7 +1,7 @@ steps: - block: "Release build" - branches: - - main + # branches: + # - main fields: - select: "Prerelease?" key: "release-type" @@ -20,8 +20,8 @@ steps: required: false - label: ":github: Trigger release" - branches: - - main + # branches: + # - main command: "bin/ci_trigger_release" agents: queue: ${BUILD_AGENT} @@ -32,3 +32,11 @@ steps: - cultureamp/aws-sm#v2.2.0: env: GITHUB_TOKEN: /cfparams/GITHUB_TOKEN + +notify: + - slack: + channels: + - "#team_sre_foundations_alerts" + message: ":fyii: : A new version of CFParams is ready to be released :shipit:" + if: build.state == "blocked" + # if: build.branch == "main"