Provide everyone in your team with the right information

Software development teams are much larger than the engineers that write code. Writing and deploying code are often only the tip of the iceberg. A well oiled software team will often consist of:

  • Development Engineers
  • DevOps Engineers
  • Support Engineers
  • Development Managers
  • Product Managers
  • A Marketing Team
  • A Sales Team
  • Executive Management

All of these people need to know something about what the software development lifecycle is producing and shipping but the level of information can vary dramatically based on a team members position. Sleuth was built to automatically generate information to satisfy each team members needs.

Project dashboard

The project dashboard is great for getting a quick sense of what’s been delivered in a period of time.

img_screenshot_mainThis is where a Development Manager can get a real sense of how their team is running. How often are you shipping code? Who’s getting work out? What exactly are you shipping? How many deploys did it take to get a stable code change out? Are you putting out large changes or are they small, incremental changes? The dashboard allows you to see answers to all these questions quickly and easily.

Email reports

Sleuth can generate and send email reports for every deploy, all deploys in a day, in a week, in two weeks or four weeks. For support engineers it’s important to know when customer facing issues are resolved. Subscribing to every deploy allows these team members to be immediately informed when a change is rolled out. Product Managers are often concerned with the wholistic view of a project. A weekly rollup of everything deployed is a great way for them to stay abreast. Marketing, sales and execs need to stay on top of the zoomed-out big picture, bi-weekly or monthly updates provide them with exactly what they’re looking for.

ChatOps release notes

Sleuth can be configured to post a deploy summary into your ChatOps channels via Slack or HipChat.


This lets your Development engineers know when their code has shipped and alerts your DevOps engineers to be on the lookout for any site reliability issues related to the change. It’s also a wonderful way to inform your wider organization about changes being made to your production environments.

Powerful search

Being able to narrow down deploys by date is what the project dashboard is all about. For Developers trying to track down a new bug it’s important to find the code that that created it. However, sometimes you remember the pull request title, or maybe the commit message for the change you need to track down. This is when search comes to the rescue. All pull request summaries, commit messages, issues titles, filenames changed and authors are indexed so it’s simple to quickly find the deploy you’re looking for. Want to know when you rolled out the Django 1.9 upgrade, just head over the search page and find out.

Provide everyone in your team with the right information

One of the hardest things about shipping software is communication. Providing different team members with the right information isn’t always easy. If you’re tracking your work using GitHub or Bitbucket then let Sleuth do the heavily lifting of putting that information into your software teams hands.

Provide everyone in your team with the right information

Track what you’re about to deploy

One of the best things about tracking deploys is knowing what and when code is shipped.

Just as important is knowing what you’re about to ship. Now when you push code to your deployment branch Sleuth will show you what you’re about to ship.


When your project has undeployed code you’ll be presented a notice that allows you to browse your undeployed changes. All the goodness you’ve come to expect from your deploy view, pull requests, commits, issues, files and authors are there to inform your upcoming deployment.

If you’ve setup your ChatOps integration then Sleuth will ping your deployment room 30 minutes after it’s detected the change, everyone needs some time to let their builds pass, right?

Happy deploying,

The Sleuth team

Track what you’re about to deploy

A deploy-based view of your software

It’s reasonable to say that we’re currently living in a world where continuous delivery is best practice for software development and delivery. However, in a world where we’re deploying software anywhere from once every two weeks to ten times a day, our tooling for truly understanding what’s being shipped has lagged behind our process. Sleuth was built to bridge this gap and to make this information available to your entire software development team.

If you’re not familiar with continuous delivery there’s an excellent summary from ThoughtWorks Chief Scientist Martin Fowler:

You’re doing continuous delivery when:

  • Your software is deployable throughout its lifecycle
  • Your team prioritizes keeping the software deployable over working on new features
  • Anybody can get fast, automated feedback on the production readiness of their systems any time somebody makes a change to them
  • You can perform push-button deployments of any version of the software to any environment on demand

Let’s assume that you’re doing it all, continuous delivery, frequent deployments, your code lives in Git, it’s being written and reviewed via pull requests, and you’re referencing issues in your commit messages. How do you answer the question of what, exactly, shipped today? How about this week? How many times did you deploy code this week? When exactly did the resolution of issue #134 find it’s way into production? Who were the authors of all those changes?

Existing tools such as GitHub and Bitbucket do an amazing job of storing our code, providing the facilities to do meaningful code review and allowing us to track our issues. All of the raw data we need to answer our deployment questions are there. What we need, however, is a deploy-centric view of our code base. One that developers, product managers, support staff, management and our customers can easily grok and consume.

Sleuth integrates with your GitHub or Bitbucket repositories and provides the deploy-centric view of your code that allows you to answer the question, what’s shipped?


By making a simple POST to Sleuth or setting up your project for auto-tracking you tell Sleuth each time you deploy a revision of code. Sleuth then analyzes your code changes to extract the pull requests, commits, issues, files and authors that made up your deploy. A deploy-centric summary is created for each deploy. It includes quick links to the full code diff on either GitHub or Bitbucket and indexes all of the information so you can quickly search and find the deploy you’re looking for.

The real power’s revealed over time and with aggregation. You can easily see how often your team’s deploying, how many pull requests you’re shipping and what your bug fix cadence looks like. Execs can subscribe to a weekly email digest that provides them with a zoomed out view. Marketing can stay abreast of what the development team is shipping. Managers have a great view of their teams “real” delivery cadence. Developers can see when their code ships to production and what changed on the day a new bug was reported. Support teams can easily search to see if a bug fix has shipped to customers. You can pipe each deploy into your ChatOps rooms for broad visibility. Your entire team is empowered with information.

Knowing exactly what shipped and when is power!

Start tracking your deploys on Sleuth and fill in the missing tool for your continuous delivery.

A deploy-based view of your software

Push your release notes straight to Slack or HipChat

One of the best things about tracking deploys is knowing what and when code is shipped.

Often it’s not just your team that wants this information. Let Sleuth generate your release notes and post them to your team communication channels.


You can now setup your deployments so that each deploy will post a summary and a link to the full deploy details into your team channel.

To enable this feature navigate to your deployment and choose “Configure Slack/HipChat Integration”


Once you’ve setup your webhook URL you can choose to enable the Slack notification for every deploy


Once you deploy you’ll see your release summary in your channel


Happy deploying,

The Sleuth team

Push your release notes straight to Slack or HipChat

Setting up your deployment tracking just got a whole lot easier

Now you have the option to setup auto-tracking of deploys for your deployments.

You have two options for auto-tracking. You can setup auto-tracking by Tag or auto-tracking by push.

Auto-tracking by Tag will install a post push hook into your repository. Each time you push we’ll inspect your push to see if you pushed a Tag. If so, we’ll create a deploy using that Tag as the ref.

Auto-tracking by push assumes that every push to your branch should be treated as a deploy. This option also installs a post push hook into your repository and inspects each push, using the pushed ref to create the deploy.

You still have the option to alert Sleuth about deploys manually by making a POST to the register_deploy endpoint.

You can setup the tracking type when you create a deployment


You can also change the tracking type for an existing deployment


Happy deploying,

The Sleuth team

Setting up your deployment tracking just got a whole lot easier