By popular demand, we’re happy to announce that we’ve made some tweaks to Slack notifications coming from Semaphore.
Here’s what our build and deployment notifications now look like:
We experimented with different approaches, ranging from minimal to multi-line, rich format messages, and used them for our projects for several weeks. In the end, we settled on a minimal, yet informative single-line format that includes all the key information (what, where) and links to relevant resources.
Deployment is everyone’s success
If you’re using Slack, and you haven’t had the chance to set up your Semaphore notifications, now is a great time to do that. All it takes is a few clicks, and it can help keep everyone in the team informed about what everyone else is working on. Learn how to set up Semaphore Slack notifications here.
We recommend setting up deployment notifications for production to a common Slack channel, such as #engineering or #general. Regardless of whether you ship weekly or continuously, every time you deliver something to your users, it’s a moment of accomplishment that’s worth sharing with the entire team.
Our internal settings are currently set to send notifications when build status of master branch changes (when it fails and recovers) and after deployment to production. Watch this quick video to see what our notifications look like in action:
If your team is not yet practicing continuous deployment, here’s an overview of how it works, and if you’re ready you can look into options for setting up deployment on Semaphore. Even just starting with a central manual trigger and history of deployment within your CI process is a great first step towards more complete automation.