Skip to content

[ML] Send version-bump Slack notification to #machine-learn-build and #ml-core - #3139

Merged
edsavage merged 2 commits into
elastic:mainfrom
edsavage:fix/version-bump-slack-both-channels
Aug 5, 2026
Merged

[ML] Send version-bump Slack notification to #machine-learn-build and #ml-core#3139
edsavage merged 2 commits into
elastic:mainfrom
edsavage:fix/version-bump-slack-both-channels

Conversation

@edsavage

@edsavage edsavage commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Summary

send_slack_version_bump_notification.sh posted the version-bump PR notification to a single channel (#machine-learn-build). Buildkite's slack notify already accepts a list of channels, so this renders one YAML list item per channel and defaults to both #machine-learn-build and #ml-core.

  • ML_CPP_VERSION_BUMP_SLACK_CHANNEL now takes a comma-separated list (was a single channel); entries are trimmed and empty ones skipped.
  • Applies to both notification paths (patch bump and minor freeze).

Heads-up (operational)

Buildkite's Slack integration only delivers to channels the Buildkite Slack app is connected to — otherwise the post is silently dropped for that channel. #ml-core is a private channel, so the Buildkite Slack app must be explicitly invited (public #machine-learn-build works without it). Done — the app has now been added to #ml-core.

Test plan

  • bash -n clean
  • Rendered the generated pipeline YAML via a buildkite-agent stub for both WORKFLOW=patch and WORKFLOW=minor; channels parses as ['#machine-learn-build', '#ml-core'] and the notify block is valid YAML
  • Next version-bump build posts to both channels (subject to the Slack-app connection above)

Made with Cursor

… #ml-core

Buildkite's slack notify accepts a list of channels; emit one YAML list item
per channel and default to both #machine-learn-build and #ml-core. The
ML_CPP_VERSION_BUMP_SLACK_CHANNEL override now takes a comma-separated list.

Co-authored-by: Cursor <cursoragent@cursor.com>
@elasticsearchmachine

Copy link
Copy Markdown

Pinging @elastic/ml-core (Team:ML)

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Buildkite version-bump Slack notification pipeline generator to support notifying multiple Slack channels from a single build, using Buildkite’s slack notifier channel list.

Changes:

  • Extend ML_CPP_VERSION_BUMP_SLACK_CHANNEL to accept a comma-separated list (with trimming and empty-entry skipping).
  • Render the resulting channels as YAML list items and use them in both notification paths (minor freeze and patch bump).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .buildkite/pipelines/send_slack_version_bump_notification.sh
…polation

Each ML_CPP_VERSION_BUMP_SLACK_CHANNEL entry is now checked against an allowlist
of characters valid for a Slack notify target (#chan, @user, IDs, [token]#chan)
and the build fails fast on anything else, so a malformed override cannot emit
invalid pipeline YAML or inject steps.

Co-authored-by: Cursor <cursoragent@cursor.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

@edsavage
edsavage merged commit 54502fe into elastic:main Aug 5, 2026
24 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants