CI/CD with GitLab
Pipelines, runners, stages, artefacts and automated deployment with GitLab CI. Industrialise your deliveries end to end.
- Design a CI/CD pipeline
- Automate tests and builds
- Manage artefacts and environments
- Deploy continuously and safely
- Ship code to production within minutes of a push, with no manual intervention
- Detect regressions automatically before they reach production
- Build a clean, maintainable multi-stage pipeline (lint, test, build, deploy)
- Measure your team's delivery velocity and identify bottlenecks
The programme
Day 1 - Continuous integration with GitLab CI
- CI/CD concepts: pipeline, stage, job, artifact, cache
- .gitlab-ci.yml: full syntax, includes, extends, rules
- Runners: shared, group, project, Docker and Kubernetes executor
- Tests, code coverage and merge request reports
- Workshop: complete CI pipeline - lint → test → build → Trivy scan
Day 2 - Continuous deployment & environments
- Variables, secrets and masked CI/CD variables
- Environments, deployments and reviews
- Kubernetes deployment from GitLab CI (kubectl / Helm)
- Strategies: canary, blue-green, feature flags
- Final workshop: complete CD pipeline to Kubernetes with automatic rollback
Who is this for
Developers, ops and DevOps engineers.
Prerequisites
- Good command of Git
- Basics of a scripting language
Format
Frequently asked questions
Which version of GitLab is used?
GitLab.com (GitLab 17, cloud) for the labs. If you have a self-hosted GitLab instance, we can adapt the workshops to your version for in-company sessions.
Does the course cover GitLab Runner on Kubernetes?
Yes, a dedicated module covers deploying GitLab Runners on Kubernetes and running pipelines in Docker-in-Docker pods.
Is the course eligible for OPCO or CPF funding?
No. Sphinx-Digital is not Qualiopi certified and is not listed on Mon Compte Formation. The course is invoiced directly to the company or the individual, with no external funding.
What is the difference between the public (inter-company) and in-company formats?
In the public format, you join a session with participants from other companies (3 to 10 people). In-company, we run a session dedicated to your team, on your site or remotely, with content adapted to your context. In-company pricing is available on quote.
Remote or on-site: what are the practical differences?
Content and labs are identical. Remotely, labs run on cloud environments accessible from a browser, with nothing to install. On-site, you provide the workstations; labs can run in the cloud or locally depending on your infrastructure.
How many participants per session?
3 to 10 participants at most. This deliberate limit ensures everyone can ask questions, adapt the exercises to their context and get a detailed answer.
What is the evening format?
The evening format spreads the same course over 4 sessions of 3.5 hours (14 hours in total), in the evening from 6:30 pm to 10:00 pm. Same content, same labs, same price, so you can build skills without taking days off.
How does payment work?
Courses are invoiced on quote, by bank transfer. Payment in instalments is possible. We issue a training agreement for companies that want their training department to cover the cost.
Interested in this course?
Join the next session or request a tailored in-company session.
What participants say
GitLab CI/CD course for a team of 8 developers. Khaled adapted the content to our stack. From-scratch pipeline to production in 2 days. Immediate ROI on our delivery times.CI/CD
Not sure this course fits your context?
A 20-minute call to take stock before you enrol, with no sales pitch.