Skip to content

ci: add team Slack mention to version bump pipeline notifications#19202

Open
ninalee12 wants to merge 1 commit into
elastic:mainfrom
ninalee12:update-slack-message
Open

ci: add team Slack mention to version bump pipeline notifications#19202
ninalee12 wants to merge 1 commit into
elastic:mainfrom
ninalee12:update-slack-message

Conversation

@ninalee12

@ninalee12 ninalee12 commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Add team Slack mention to the blocked-state notification so the team is pinged when the version bump pipeline needs manual approval
  • Add team Slack mention to the pass/fail notification so the team is informed of pipeline completion or failure

Context

Version bump pipelines are triggered centrally by the centralized-version-bump pipeline. Previously, only the release engineer who triggered the pipeline was notified — leaving teams unaware when their pipeline was waiting for approval or had finished.

Feel free to suggest a different Slack handle or a dedicated person to ping if this isn't the right one for your team.

Test plan

  • Verify Slack notification in the team channel includes the team mention on next version bump run

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
  • run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

@mergify

mergify Bot commented Jun 10, 2026

Copy link
Copy Markdown
Contributor

This pull request does not have a backport label. Could you fix it @ninalee12? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • If no backport is necessary, please add the backport-skip label

@elasticmachine

Copy link
Copy Markdown

💛 Build succeeded, but was flaky

Failed CI Steps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants