Operations | Monitoring | ITSM | DevOps | Cloud

CI CD

The latest News and Information on Continuous Integration and Development, and related technologies.

DevOps is dead? Nope, it is maturing ft. Jesse Robbins of Heavybit

In this episode, Rob sits down with the DevOps “party starter” himself, Jesse Robbins, to discuss the current state of software delivery. Is DevOps really dead, or are we simply witnessing a maturing model as organizations grow and evolve? Tune it to hear Jesse’s valuable take on where he sees the industry moving and the potential complexities on the horizon.

Improve engineering teams faster with DORA metrics

We talk with numerous teams that want to improve their engineering performance. Here, we explain how to accelerate your progress using DORA metrics — a set of key performance indicators that can help you measure and optimize your team's software development process. You'll learn practical tips on how to leverage these metrics to achieve faster and more efficient team improvement. But first, you'll need your team to see the value in DORA metrics.

Optimize your CI/CD Pipeline with Coralogix Tagging

Continuous Integration/Continuous Delivery (CI/CD) has now become the de-facto standard for all engineering teams seeking to keep pace with the demands of the modern economy. At Coralogix, we operate some of the most advanced build and deploy pipelines in the world. We’ve baked that knowledge into our platform with a CI/CD Observability feature called Coralogix Tagging.

Unhealthy code? Don't rely on customers to tell you

Does your software deployment process require that someone on your team manually checks different dashboards to verify that everything's okay? Do they actually do that when they deploy? Do you rely on customer complaints to notify you when something's wrong? There's a better way: Sleuth CTO and co-founder Don Brown shows you how to track several health measures automatically in Sleuth.

AMA: Achieving code reliability across the release cycle

Code coverage, arguably a very important measure that we as development teams don’t pay enough attention to. That is until Sentry notifies you of a frustrating/critical/oh s*#t moment. Then we all think: “how could this have been avoided?”, “why didn’t our tests catch it?”, “oh… we didn’t have any coverage on this flow.” With our new Codecov integration, you can avoid regressions (and awkward conversations) by being able to see which lines that caused an issue are covered and which ones are not - right in the stack trace we kick out on every error report.