Does it support security scanning for every image?

Yes. For every image defined in the matrix, the skill automatically configures Hadolint for Dockerfile linting and Trivy for vulnerability scanning, ensuring all your containers are secure and follow best practices.

What does the Multi-Dockerfile Build skill do?

This skill automates the configuration of GitLab CI pipelines to build, lint, and scan multiple Docker images simultaneously. It leverages the To-Be-Continuous Docker template and GitLab's parallel matrix feature to handle complex multi-container projects efficiently.

Which build tools are compatible with this skill?

The skill is compatible with Kaniko, Buildah, and Docker-in-Docker (dind). It includes optimized caching strategies for Kaniko to significantly speed up your pipeline execution times.

How does this skill improve my DevOps workflow?

It eliminates manual CI/CD configuration for each container, reduces total pipeline duration through parallelization, and provides a centralized way to manage build arguments, metadata, and SBOM generation for your entire container suite.

When should I use this skill?

Use this skill when you have a monorepo or a project with several Dockerfiles (e.g., frontend, backend, and worker) that need to be built and pushed to a registry from a single GitLab project.

Multi-Dockerfile Build

Name: Multi-Dockerfile Build
Author: rafaelcalleja

byrafaelcalleja

•

Despliegue y DevOps

Configures GitLab CI pipelines to build and scan multiple Docker images in parallel using the To-Be-Continuous Docker template.

Multi-Dockerfile Build

byrafaelcalleja

•

Despliegue y DevOps

Configures GitLab CI pipelines to build and scan multiple Docker images in parallel using the To-Be-Continuous Docker template.

Acerca de

Enables efficient multi-container builds within a single GitLab project by leveraging the parallel:matrix feature of the To-Be-Continuous (TBC) Docker template. This skill provides the necessary configuration patterns to manage complex monorepos—such as those containing frontend, backend, and worker services—ensuring each image undergoes standardized linting, security scanning, and SBOM generation while maximizing pipeline speed through concurrent execution.

Características Principales

Parallel execution of multiple Docker builds via GitLab CI matrix configuration
Automated Software Bill of Materials (SBOM) generation for all containers
Support for Kaniko, Buildah, and Docker-in-Docker build tools with optimized caching
Automated security scanning with Trivy and linting with Hadolint for every image
Centralized management of build arguments, metadata, and publishing strategies
1 GitHub stars

Casos de Uso

Implementing consistent security and linting standards across multiple microservices
Building frontend, backend, and worker containers simultaneously in a monorepo
Optimizing GitLab CI pipeline performance for multi-service architectures

Acerca de

Características Principales

Parallel execution of multiple Docker builds via GitLab CI matrix configuration
Automated Software Bill of Materials (SBOM) generation for all containers
Support for Kaniko, Buildah, and Docker-in-Docker build tools with optimized caching
Automated security scanning with Trivy and linting with Hadolint for every image
Centralized management of build arguments, metadata, and publishing strategies
1 GitHub stars

Casos de Uso

Implementing consistent security and linting standards across multiple microservices
Building frontend, backend, and worker containers simultaneously in a monorepo
Optimizing GitLab CI pipeline performance for multi-service architectures