GitLab CI

When we talk about GitLab CI, it's common to immediately think about stages and jobs in a pipeline. However, the goal here isn't to dive into the details of each step, but rather to understand GitLab CI as an essential tool within the software lifecycle. Let's look beyond pipelines and explore how the .gitlab-ci.yml can bring value to your project and team as a whole, helping to structure an efficient and scalable continuous delivery process.

Don't forget to read the introduction about pipelines to better understand the concepts we'll discuss here.

GitLab CI/CD has become one of the most relevant tools in the DevOps world, especially when talking about pipeline automation. Natively integrated with GitLab, it allows teams to version code, run tests, build, and deploy continuously and in a controlled manner, all within a single flow.

In a scenario where the pursuit of fast, secure, and consistent deliveries is increasingly constant, GitLab CI stands out for its simplicity of configuration via .gitlab-ci.yml, native integration with the repository, and the ability to scale alongside the development team.

In a way, GitLab CI is to GitLab what GitHub Actions is to GitHub. If your code repository is on GitHub, GitHub Actions will certainly be the most suitable tool. However, if you use GitLab, understanding how GitLab CI works will be essential to leverage its full potential.

One of the great advantages of GitLab CI is the ease in declaring pipeline steps. However, before we understand how this works in practice, it's important to first understand the basics about GitLab and how it integrates into this process.

What is necessary to continue advancing during the course?

• Understand Git and what Git repositories are. If you don't have this familiarity then this course is not for you. Seek some knowledge about Git here on the site to get started.
• An account on Gitlab