In the last installment of the Hoptoad Chronicles, we introduced the deploy tracking feature. We also mentioned that this feature paved the way for a bunch of great improvements we’d be able to roll out.
Like most of the community, we use GitHub for all of our projects. We figured out that we can use the information gleamed from Capistrano during the deploy process to integrate GitHub into your error reports.
If you’re using the deploy functionality, then you’ll see the git revision listed when you view the deploys for a project. The revision links straight to the exact tree that was deployed.
But wait! There’s more!
Even better, when you view an error that happened while a deploy was active, you’ll see that some of the lines of the backtrace are links. These point straight at the exact line in the backtrace on GitHub:
Now that we’ve rolled out deploy tracking, the RAILS_ENV that an error came from is even more important than it was before. We’ve made an improvement there by changing that text to a link that lets you see just the errors that came from that environment.
Above and Beyond
Before we rolled out deploy tracking, we’d gotten many requests for bulk resolving exceptions. It was clearly a pain point, but we wanted to wait on a solution until we fully understood the reason people needed this feature. Adding deploy tracking was much more effort for us, but serves the end user much better and didn’t add clutter to the UI.
In general, we believe it’s better to take the long road and produce a cleaner and more useful application, than take the easy road and produce something mediocre.
Try out a 30 day free trial of a HopToad paid account to make use of these great new features!