Keep your teams and other principals informed throughout the entire CI/CD lifecycle by using Slack as your main communication channel. No more bloated distribution lists, and bombarding your team with a barrage of emails. Use Slack's powerful communications features to keep development teams informed about your code deploys, and your entire organization up to date on progress.
Agile teams will spend most of their time viewing the Dashboard to get the granular detail they need to stay informed on the status of deploys, impact, magnitude, and the breadth and scope of information Sleuth provides. Other members of your organization, however, might only want a quick update on your team's progress without getting into the weeds. Slack messages provide just that—automated, easily-digestable messages where they can view:
when your deploy occurred;
what was deployed;
who the author was;
how big the deploy was;
the commit hash;
how many commits, PRs, issues, and changes were in the deploy;
any Jira issues associated with the deploy; and
a link to the Sleuth deploy card, where even more information is available.
Before you start, you should already have a Slack account. Additionally, you should create channels that you plan to use for messaging in Slack before setting up the integration. Sleuth will ask for the Slack channel where it should send its messages to. You can create as many channels necessary to target various groups or individuals. You might have different audiences, who might have different needs.
Slack integration is setup and configured in a Sleuth organization. All Sleuth projects created within the Sleuth organization have access to the configured Slack space. This enables Slack notifications to be broadcast to everyone who has access to the Slack space. When a channel is configured with a Sleuth project, anyone who follows that Slack channel will receive all messages sent to that channel.
Sleuth can also be setup to send individual Slack messages. For example, instead of broadcasting a message to all channel subscribers of a commit, pull request or a locked repo, you might only want to notify the author (or all authors who made at least one commit), or only the individual who initiated the deploy.
Click Integrations in the sidebar.
In the Chat Ops > Slack card, click enable.
Click Allow to make the integration.
4. Upon a succesful connection to your Sleuth account, the message Slack enabled (Connected to workspace <workspace name>) is displayed in the tile.
Sleuth will now use Slack to relay important deploy information to your team, as well as individual notifications to commit authors and/or deploy initiators.
With the Slack integration made to your organization, you can fine-tune Slack notifications within each project. Depending on how many Sleuth projects you have and the various teams working on those projects, it might be the case that not every person in configured organization will want to receive notifications on projects they're not working on.
Select the project you wish to modify in the project dropdown in the sidebar.
Click on Project Settings, then click Slack Notifications.
Start typing the name of the channel you wish to broadcast to in the Slack channel field. A list of available channels will auto-populate. Select the preferred broadcast channel for the project you're currently in.
The selected Slack channel will start receiving deployment notifications similar to the one shown below:
Personal Slack notifications means that you'll be notified instantly when your code or changes that you were involved in ship. No more long-polling your build system to see if that code finally made it out to production, or checking your Jira instance to see if the issues have been moved to Done.
If you've configured Impact for your deploys and Sleuth detects that your change was unhealthy, you'll know moments after deploy. You'll be to see the impact of your changes in real-time, all directly from your Slack client.
When you receive a deployment notification in Sleuth, you can:
Click View deploy to view all detailed information that led up to the deployment.
Clickto view a dropdown (see screenshot below) that displays detailed deployment information, including:
All authors involved in the deployment. Opens the Authors tab in Sleuth
All the diffs (changes) that comprised the deployment. Opens the change compare section of your code repository (i.e., Bitbucket, GitHub, or GitLab)
All the pull requests that comprised your deployment. Opens the Authors tab in Sleuth
All the issues created during the deployment. Opens the Issues tab in Sleuth
All the builds that ran during the deployment. Opens the Builds tab in Sleuth
Click on Integrations in the left sidebar, then on Chat Ops.
In the Slack integration card, click disable. The message Slack disabled is displayed in the Slack integration card once the integration is dissolved.
The Slack integration is disconnected and no longer available to any projects within that organization. Any project-level modifications you made to the Slack integration will be lost.
If your organization has a Slack integration, you can use the Slack app to search through your deploy history.