Notifications
Buddy integrates with the most popular messaging services to ensure your team is always up-to-date with the progress in the project:
Notification actions in Buddy
About notifications
Notifications are usually added at the end of the delivery pipeline as a summary of the executed actions:
Pipeline example
Each notification action contains a default message with essential pipeline details: pipeline name, execution ID, and invoker. The details are generated with default Buddy variables:
[#$BUDDY_EXECUTION_ID] $BUDDY_PIPELINE_NAME execution by <$BUDDY_TRIGGERING_ACTOR_URL|$BUDDY_TRIGGERING_ACTOR>Most notification actions support attachments. In case of Slack, you can also define content blocks, as shown on the screenshot below:
Default Slack notification preview
And here's how the message looks rendered in the Slack's window:
Notification from Buddy in Slack
Conditional notifications
To prevent filling your inbox or channel with unwanted spam, you can configure Buddy to inform you only in certain cases. The most common use case is sending a message only when your tests or deployment have failed.
To do that, add the notification to the On Failure scenario of the pipeline:
On failure notification pipeline example
To let your team know that the pipeline status has gone back from 'Failed' to 'Successful', you can add another notification to On Back to Green:
Back to normal notification example
Notification action settings
Advanced conditioning
You can add an extra set of trigger conditions in the Conditions tab. The options let you send notifications, for example, on changes to a specific path (e.g. when somebody modifies the /assets folder), or depending on the value of an ENV VAR (e.g. $BUDDY_TRIGGERING_ACTOR – when you have that one developer you need to keep an eye on):
Advanced trigger conditions
Sep 17, 2024