Dockerize the build plan v2.0

Update: This post is now available at a new location:
https://blog.ngeor.com/2018/08/26/dockerize-the-build-plan-v2-0.html

Back in 2017, I wrote a series of articles about using Helm for Continuous Delivery. One year later, I want to look back on some things I wrote and offer some alternative solutions. The most interesting thing is about the article CD with Helm part 2: Dockerize the build plan.

Continue reading Dockerize the build plan v2.0

Advertisements

CD with Helm part 5: versioned artifacts

Update: This post is now available at a new location:
https://blog.ngeor.com/2017/12/02/cd-with-helm-part-5-versioned-artifacts.html

In the previous post we created the Helm chart for our hello world blog-helm application. The Helm chart contains all the information we need to deploy our application to a Kubernetes cluster. But so far, we always deploy the latest version. In a CD setup, we’d like to be able to deploy any version, from any feature branch, at any given point in time, to any environment (DTAP). Let’s start by looking at versioning.

Continue reading CD with Helm part 5: versioned artifacts

CD with Helm part 3: Kubernetes Intro

Update: This post is now available at a new location:
https://blog.ngeor.com/2017/11/25/cd-with-helm-part-3-kubernetes-intro.html

In the previous posts we took the first steps to dockerize our hello world application. This allows us to run the application on any host, as long as it runs Docker. We also dockerized the build plan, which allows us to use any build server, as long as it runs Docker. Now we’re ready to run the application on production. Where should we run it?

Continue reading CD with Helm part 3: Kubernetes Intro

CD with Helm part 2: Dockerize the build plan

Update: This post is now available at a new location:
https://blog.ngeor.com/2017/11/18/cd-with-helm-part-2-dockerize-the-build-plan.html

With Docker, we can package our application in a Docker image and we have the assurance that it will run on any machine that has Docker. We can do the same with our build plan. Dockerizing the build environment means that the only dependency we have on the build server is that it supports Docker. This reduces the amount of work needed to manage the build server and enables teams to be more independent.

Continue reading CD with Helm part 2: Dockerize the build plan

CD with Helm part 1: Dockerize it

Update: This post is now available at a new location:
https://blog.ngeor.com/2017/11/15/cd-with-helm-part-1-dockerize-it.html

In the previous post, we created the hello world application that we’ll be using. Now it’s time to dockerize the app. Dockerizing means to create a Docker image that can be used to run the app.

Continue reading CD with Helm part 1: Dockerize it

CD with Helm part 0: hello world app

Update: This post is now available at a new location:
https://blog.ngeor.com/2017/11/13/cd-with-helm-part-0-hello-world-app.html

I’d like to start a tutorial series on how to apply CI/CD principles with tools like Kubernetes and Helm. I’m extremely new in these technologies, so this is a learning exercise for me.

Continue reading CD with Helm part 0: hello world app

On git branching models

Update: This post is now available at a new location:
https://blog.ngeor.com/2017/09/23/on-git-branching-models.html

Usually, when you work with a version control system like git, development happens in multiple branches. It’s funny to see people’s faces when you tell them that the author of Continuous Delivery, Dave Farley, advocates “no branches”. I had that same surprised face myself the first time I heard that concept. But, so far, I haven’t really worked somewhere where no branches were used.

Continue reading On git branching models