Why move up to advanced GitLab CI/CD skills?
Setting up a working GitLab pipeline is accessible; designing a robust, secure, performant and maintainable pipeline at the scale of an organization requires a much deeper mastery. Teams dealing with multi-environment delivery chains, complex release strategies or compliance constraints need advanced patterns: parallelization, optimized cache, parent/child pipelines, dynamic environments, conditional rules, integration with Docker, Kubernetes or Terraform.
What this training adds on top of GitLab Fundamentals
The GitLab CI/CD Advanced training assumes the basics are mastered. It focuses on industrialization patterns: pipeline splitting, reuse through includes and templates, fine-grained management of variables and secrets, deployment strategies (canary, blue/green), interactions with external registries, and optimization of execution times. It also prepares profiles aiming for the GitLab Associate certification (GLB-10) by providing a practice level well above basic requirements.
Why take this training in person or virtual rather than through tutorials?
Online tutorials often cover simple and dated cases. In the enterprise, complexity comes from the intersection of several constraints (security, performance, maintenance, traceability). This course offers scenarios inspired by real projects, compared architecture choices and feedback from a practicing instructor. You leave with a decision framework, not just commands.
Practical tips to consolidate what you learn
After the training, apply the patterns seen in class to a real project in your organization: start by factoring an existing pipeline with includes, then gradually add cache, conditional rules and a review environment. Regularly revisit the official GitLab documentation, which evolves quickly.
FAQ
Should I have taken GitLab Fundamentals before this training?
It is strongly recommended. Failing that, 6 to 12 months of operational experience with GitLab CI/CD on at least one project is expected.
Does this training cover GitLab runners?
Yes, runner configuration, tags and execution strategies (shared, group, project runners) are covered in the advanced context.
Can the content be transposed to other CI/CD tools like GitHub Actions?
The concepts are largely transferable (stages, jobs, variables, artifacts). The syntax and some native features remain GitLab-specific.
Does the training address DevSecOps and security scanning?
SAST/DAST/dependency scanning concepts are introduced. For deeper DevSecOps coverage, the DevSecOps Fundamentals training (SEC-01) is recommended as a complement.