Tracking Deployments with Rollbar


At Codeship we are quite heavy users of Rollbar, a fantastic service that “collects and analyzes errors on web and mobile apps so you can find and fix them faster”. They also provide you with an API to track deployments of your application. This allows you to gain more insight into your deployments, without you having to spending a lot of effort. You can, for example, track errors over multiple deployments and see if they got resolved or are happening again.

Of course, an optimal (Continuous) Deployment tool should integrate Rollbar (and every other useful service) directly. It should not force you to use shell commands. But as services come and go and development teams are limited, sometimes you have to do it yourself.

Pushing Deployment Information with Rollbar

Here is the command the team at Rollbar suggests to push deployment information to their service.

This should be extremely to easy to integrate into almost any deployment process. And the Rollbar team additionally provides a bunch of other integrations with tools such as Capistrano or Fabric in their documentation.

If you integrate this command into your deploy pipeline you get nice annotations in your graphs as well as an extremely well done integration throughout the rest of the app. For example Rollbar tries to figure out which deployment is responsible for a certain exception.

Tracking Deployments for one of Codeship's services with Rollbar

How Rollbar helps Codeship

We use Rollbar in all of our services. Of course we also track the deployments of these services. Most of the time we use it with a shell command quite similar to the one above, sometimes integrated with similar commands for other services. More than once this integration has helped us drill down into a certain exception so we could figure out which commit introduced it and how to fix it. Try Codeship – The simplest Continuous Integration service out there.


We want to thank the Rollbar team around Brian and Cory for their awesome service. If you are looking to integrate an exception tracking service into your application, make sure to check them out. Are you a Rollbar user? I would love to hear your thoughts in the comments!

Further Information

Subscribe via Email

Be sure to join over 40,000 subscribers of our newsletter to receive updates on software development best practices, Continuous Delivery and tips and tricks to start shipping your product faster.

We promise that we won't spam you. You can unsubscribe any time.

Join the Discussion

Leave us some comments on what you think about this topic or if you like to add something.

  • Pingback: Tracking Deployments with Rollbar – Free Snippet | Open World()

  • timdorr

    Here’s a Rake task you can also use for the same purpose if you’re using Ruby and/or Rails:

  • Dries Vints

    Why do you prefer Rollbar over Bugsnag? Are there specific reasons?

    • Florian Motlik @codeship

      The interface gave us a lot better overview on problems that were happening. At the time Rollbar moved along much faster than bugsnag. Don’t know about their current pace and featureset though

  • Mobile Pundits

    Grab this free re-usable snippet to integrate Deployment Tracking with Rollbar into your Deployment Process. Good one.
    Mobile app testing