ci(NOJIRA-1234): align frontend deploy notifications with backend format#202
Draft
kb-typeform wants to merge 5 commits intomainfrom
Draft
ci(NOJIRA-1234): align frontend deploy notifications with backend format#202kb-typeform wants to merge 5 commits intomainfrom
kb-typeform wants to merge 5 commits intomainfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Align frontend deploy Slack notifications with the backend one-liner format used in
#tfprod-deploy, so both backend (Jenkins) and frontend (GitHub Actions) messages look consistent in the same channel.Changes
🚀 app:sha was deployed to production by actor (CDN)🔥 The deployment of app:sha to production by actor has failed (logs) @teamteam-slack-handleinput for team mentions on failure (mirrors JenkinsTEAM_SLACK_HANDLE)cdn-urloptional (still included in success messages when provided)github-ref-nameinput (branch info no longer shown in compact format)Context
Backend deploy messages in
#tfprod-deployuse a compact one-liner format from jenkins-shared/pipelines/deploy-backend/Jenkinsfile. The frontend notifications previously used verbose Slack Block Kit cards with headers, fields, and buttons — visually inconsistent when both land in the same channel.