As a software developer or tester it’s important to know
about the testing pyramid because it will help
make decisions about the types of testing that
each project requires. Not all types of tests
are the same, some are fast while others are
slow, some impersonate an end user while others
simply test units of logic. After this post
you’ll understand the different types of tests
and why pyramids are bigger at the bottom :P
Although Docker is growing fast and is quickly gaining
a strong reputation among development teams for it’s
ability to deploy development environments in local
consistently and reliably, are companies really using
it in production and at scale? Does Swarm have all the
features needed to orchestrate containers in production?
The release of Docker 1.13 is coming up quickly, here are the top 10
things we can expect to see when it comes out:
In a previous article
we deployed a
Jenkins instance in Docker using Ansible. However after
the Jenkins is deployed we had to configure it manually
(Jenkins was a pet).
In this article we’ll look at how to automate the deploy of services
to your docker 1.12 swarm. If you’re interested in automating
the deploy of a dockerized application for Continuous Deployment or
highly automatic workflows then this is a must-read.
Docker Stacks and Distributed Application Bundles (we’ll call them
“bundles” in this post) are a way to describe multiple services
in one single file.
In this post we’ll talk about how to (and how not to)
design internal APIs so they are reusable. By “Internal APIs”
I mean the ones used only from inside your company,
by other products or components that your company has
In this post you’ll learn how to use the Jenkins Pipeline plugin
to build Docker images continuously.
There are some very good articles and posts out there which
describe in fantastic detail how Docker works and how easy
it is to start a container (now a “service” in
However not many blogs talk about the other stuff that
must be done to successfully get the application responding
to requests from the web, and less talk about a 1000 node
In this article we’ll look at how to deploy a Jekyll blog
in a Docker container.
Docker version 1.12 was released recently, this post is an overview of the goodies that
it brings as well as a breakdown of what each change will mean for you.
In a previous post we looked at how to provision a swarm cluster using Ansible.
In this post we will take the automation one step further and learn how to deploy a full
application to the cluster using docker-compose and Ansible. In order to get the most out of
this post you should already have a docker swarm up and running, but it shouldn’t matter
if you’ve provisioned it using Ansible as described in the other blog post or if you’ve
provisioned it manually. As long as you have a working swarm the commands will work.
In this blog post we’ll look at how to provision a swarm cluster on bare metal servers using Ansible. This will let you provision swarm clusters extremely easily, simply by running the ansible playbook.
As all software developers know, automating tests becomes very important as the size of the project grows and the standards rise. Automatic tests allow us to catch bugs as quickly as possible when developing software, this quick feedback allows us to iterate quickly and fix it quickly. In turn this leads to stuff getting into production quicker (since bugs are found and fixed more quickly) and it means that what does get into production has less bugs (since it passes the tests). In this post we’ll look at running end user tests in a continuous testing workflow for docker applications.
This article will help you get a ghost blog set up inside a container. First we’ll
containerize the blog and get it working on your local machine and then we’ll deploy
it to a single production ubuntu server.