Analyzing Jenkins Metrics: Track Broken Builds, Build Time and More

By Andre Newman in loggly

September 28, 2018

Implementing continuous delivery (CD) is a challenge for organizations of all sizes. It’s not just a matter of generating more builds more often, but of automating and optimizing the release process. To know whether you’ve done CD successfully, you need to understand whether you are checking in your code frequently enough, whether builds are being delivered successfully, and whether you’re making the build and delivery process more efficient.

Continue reading

Win-Win Deployment Strategies for Modern Apps

By Jason Skowronski and Sadequl Hussain in rollbar

September 12, 2018

Today, modern applications need frequent updates to deliver on business objectives with fast turnaround time. The days of months- or years-long release cycles are gone. Modern applications may be deployed on short notice multiple times per day. This gives the enterprise more agility to make changes that deliver business value faster. Now product teams can iterate on new versions of the product quickly, testing the impact on key metrics and fixing problems immediately.

Continue reading

Tracking errors after deployments with Rollbar and CircleCI

By Jason Skowronski in Rollbar

June 21, 2018

Rollbar integrates with your CI/CD system to track when deployments are promoted to production. When an error occurs, it looks up the deployed version in GitHub. You’ll be able to see the code changes that caused the error in just a few clicks.

Continue reading

Continuous Delivery with Jenkins and Rollbar

By Jason Skowronski in Rollbar

January 9, 2018

Continuous delivery (CD) helps reduce the cost, time and risk of delivering changes by allowing for fast incremental updates to applications in production. However, it’s essential to monitor your application after each deployment. You need to be notified immediately if something is wrong or users are having a poor experience.

Continue reading