Continuous integration tools like CircleCI let developers automate builds and tests, so that teams can merge changes into their codebase quickly and frequently. In this article, we’ll take a look at how to combine Sentry’s command line interface with CircleCI to automatically create Sentry releases. This will unlock some of our best features, like identifying suspect commits that likely introduced new errors, applying source maps to see the original source code within Sentry, and more.

This year marks the 8th year since we incorporated Sentry. Every year has created a new set of opportunities as we’ve expanded both our product and our customer base. We’re fortunate to be considered the market leader in error monitoring, and are aggressively building on top of that success to make software better for everyone. Our rapid revenue and customer growth, combined with recent funding, has given us the exciting opportunity to more broadly fix application monitoring.

At Sentry, we pride ourselves on having an open kitchen; everyone can see how we prepare our main dishes as an open-source company. As you may have noticed, we’ve been working hard to bring you a version that’s incredibly easy to set up and maintain: Sentry 10! It’s available today! Before you start hammering PyPI, GitHub, or Docker servers, please read on as there are important changes that need your attention.