Using AWS ECR as a Docker registry

In this post, I’ll modify the pipeline from the previous posts to use a Docker registry powered by AWS ECR (Amazon Elastic Container Registry).

Continue reading “Using AWS ECR as a Docker registry”


Adding code coverage with nyc

In this post, I’ll add code coverage to the build pipeline and configure TeamCity to break the build if the code coverage drops.

Continue reading “Adding code coverage with nyc”

Removing the image-tag.txt artifact

Small update on replacing the image-tag.txt artifact with the implicit build.number parameter.

In the post about versioned artifacts, I was using a custom text file named image-tag.txt to share the image tag between build configurations. The commit stage evaluates the image tag and produces the image-tag.txt artifact, which just contains the version e.g. 1.3.0.

After the post about the versioning script, the build number of the commit stage and the image tag where identical and they were following semantic versioning.

In a more recent post, I’ve configured a build chain in TeamCity, in which all build configurations share the build number of the Commit Stage. This means that all build configurations have the correct image tag information implicitly, as their build number. This makes the image-tag.txt artifact obsolete.

I have therefore removed the image-tag.txt artifact and I’m using the implicit configuration parameter %build.number% wherever I need it. The pull request is available here.

Host DNS in Docker Toolbox

How to configure Docker Toolbox so that it uses your laptop’s hosts file.

When playing locally on a developer’s laptop, it’s handy or needed to modify your laptop’s hosts file to fake some DNS entries. That’s C:\Windows\System32\drivers\etc\hosts on Windows and /etc/hosts on Mac/Linux. By default, Docker Toolbox won’t see these custom DNS entries. Here’s how to change that.

Continue reading “Host DNS in Docker Toolbox”