Skip to content

ci(NOJIRA-1234): align frontend deploy notifications with backend format#202

Draft
kb-typeform wants to merge 5 commits intomainfrom
feat/align-frontend-deploy-notifications
Draft

ci(NOJIRA-1234): align frontend deploy notifications with backend format#202
kb-typeform wants to merge 5 commits intomainfrom
feat/align-frontend-deploy-notifications

Conversation

@kb-typeform
Copy link
Contributor

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

  • Replaced Block Kit card format with simple text messages matching the backend Jenkins deploy format
  • Success: 🚀 app:sha was deployed to production by actor (CDN)
  • Failure: 🔥 The deployment of app:sha to production by actor has failed (logs) @team
  • Added optional team-slack-handle input for team mentions on failure (mirrors Jenkins TEAM_SLACK_HANDLE)
  • Made cdn-url optional (still included in success messages when provided)
  • Removed github-ref-name input (branch info no longer shown in compact format)
  • Removed checkout step and commit message extraction (no longer needed)

Context

Backend deploy messages in #tfprod-deploy use 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.

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.

1 participant