Continuous Delivery with Docker and Jenkins

Building Jenkins slave

Let's start from the slave image, because it's more often customized. The build execution is performed on the agent, so it's the agent that needs to have the environment adjusted to the project we would like to build. For example, it may require the Python interpreter if our project is written in Python. The same is applied to any library, tool, testing framework, or anything that is needed by the project.

You can check what is already installed inside the evarga/jenkins-slave image by looking at its Dockerfile at https://github.com/evarga/docker-images.

There are three steps to build and use the custom image:

1. Create a Dockerfile.
2. Build the image.
3. Change the agent configuration on master.

As an example, let's create ...