Skip to main content
This article explains a modern method for creating build agents using Docker containers. Instead of managing persistent virtual machines—even in the cloud—you can leverage ephemeral Docker containers that start for a specific task and then shut down. This approach greatly simplifies infrastructure management by using containers as temporary build agents. We will use Docker to launch a Go container and walk you through each step.

​
Setting Up the Pipeline

Begin by opening your VS Code and reviewing the pipeline code. The pipeline defines a development stage where it clones a Git repository and runs a command to display the Go version. The significant difference in this configuration is the specification of a Docker image for the build agent. Below is the Jenkins pipeline code that utilizes the official Go image from Docker Hub:
Historically, you may have used a freestyle project to select an Ubuntu instance as your build agent. With Docker, however, the container itself becomes the build agent. For most cases, the built-in Docker images (like golang:latest) available on Docker Hub are sufficient.
Using Docker containers as build agents eliminates the overhead of managing virtual machines and can streamline your CI/CD workflow.

​
Configuring the Pipeline in Jenkins

Once you have your pipeline code ready, follow these steps in Jenkins:
  1. Create a new item and name it (e.g., “go build”).
  2. Select “Pipeline” as the project type.
  3. Click “OK” and paste the above pipeline code into the configuration area.
The image below illustrates the Jenkins interface for creating a new item:
The image shows a Jenkins interface for creating a new item, with options like Freestyle project, Pipeline, and Multi-configuration project.
After pasting the code, save the configuration and click “Build Now” to trigger the pipeline.

​
Viewing the Build Process

When you initiate the build, Jenkins will launch the Docker container and execute the pipeline. Internally, the Docker run command is invoked to execute the go version command within the container. You can monitor the console output in the build logs to see the version of Go installed. Below is an overview of the Jenkins dashboard stage view:
The image shows a Jenkins dashboard with options like "Build Now" and "Configure," displaying a stage view with development time and build history.
Here is a sample console output from the pipeline execution:
As seen in the logs, the build process successfully clones the repository and executes the go version command inside the Docker container. Notice that the command output reports Go version 1.17.6.
If you require a specific Go version for your project, consider using a tagged Docker image (e.g., golang:1.17.6) to ensure consistency across builds.

​
Conclusion

This article demonstrated how to use Docker containers as ephemeral build agents in Jenkins. By specifying the Docker image within your pipeline script, you can achieve a more lightweight and flexible CI/CD process that leverages containerized resources without the need for managing traditional virtual machines. In the next lesson, we will explore further enhancements to containerized build processes and additional customization options for your pipelines.

Watch Video