Containerized CI supplies the build environment through containers, so developers and CI can run the same Docker-based build without installing the application SDK locally. This reduces build-server maintenance and makes pipelines easier to move between services such as Jenkins, Docker Hub, GitHub Actions, and Azure DevOps. section 11.4
A practical containerized CI build follows this workflow:
- Keep the Jenkins pipeline, Dockerfiles, Compose files, and build scripts in source control. section 11.4
- Run the same Docker Compose build command used locally, adding --pull to retrieve current base images and detect breaking image changes early. section 11.4
- Capture Docker and Compose output in the CI logs, then inspect produced images through a container registry API. section 11.4
