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.

January 29, 2020 It’s well known that within large IT datacenters, specialists in different domains (i.e. application, DB, networking, storage, etc) often struggle with sharing tools to solve problems. Vendors produce tools that may give a deep view of one domain, but lack correlation with others.

App containerization has picked up momentum in recent years as it helps to save costs, time and resources. Resource vendors are available to assist in containerization of one or two apps, but most vendors struggle to execute a large number of app containerization projects with the same skill level and outcomes. As a matter of fact, it’s a manual approach in certain scenarios with a lot of dependencies which is not only time and cost consuming but also prone to errors and miscalculations.

This is the one post I hope you’ll never need. However, should you ever need it, this is your one-stop shop for understanding how to proceed with DevOps incident management. Have you just been attacked? Did the commit go wrong? A CI pipeline went haywire? Don’t worry. I got you.

In any rapidly emerging market, consultants can be a great source for vendor-neutral insights, as they typically work with multiple technologies to help their customers make informed decisions. In that vein, Derya (Dorian) Sezen of kloia, a new-era consulting organization that provides services toward transition of legacy workloads to frontline technologies in Cloud, DevOps and Microservices, recently wrote a blog summarizing his experience with Rancher and Red Hat OpenShift.