In today’s post, we’ll go over what continuous integration and continuous delivery are, the benefits that come along with employing CI/CD, and some best practices that you should follow. We’ll also explore a wide array of Elixir ecosystem tools that can help you create top-notch CI pipelines. In order to experiment with a handful of the tools that we will be discussing, we’ll use a Git hooks Elixir library to execute our CI/CD validation steps, but on our local machine.

AIOps helps DevOps teams in multiple ways, including by boosting developer productivity, improving the customer experience, and increasing the CI/CD cycle frequency.

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.

Like in 2018, now that 2019 is gone, it is time to look back and see all the major Codefresh features that were added over the past year. The highlight of the year was, of course, the world’s first live debugger for CI/CD pipelines, a feature that makes us really proud since it changes completely the way you create and analyze CI/CD pipelines.

The DevOps infinity loop is a visualization that everyone reading this article is likely familiar with, and one that comfortably predates serverless computing. Yet despite the peculiarities of developing within the serverless paradigm, it’s still what guides our approach to CICD. But while the zoomed-out view might be the same, when it comes to adjusting for serverless, the devil is in the details.