Gitlab 1-2 Explanation of the terms below
Welcome to this first video about GitLab. In this introductory lesson we are going to learn what CI/CD means. CI stands for Continuous Integration, and CD stands for Continuous Delivery (or Continuous Deployment). This is a relatively recent concept that has gained huge popularity over the last few years, and more and more companies are adopting it.
What CI/CD actually is
CI/CD is a methodology aimed at delivering applications to clients by automatically inserting changes into the software development lifecycle. Concretely, it means automating every stage of development to minimize human intervention and, as a consequence, the number of human errors. In short, CI/CD automates integration, build, test and deployment of the code.
Why does that reduce errors? Throughout this course you will see that CI/CD makes building, developing and releasing software much easier. A developer can change lines of code that almost immediately reach the production version of the software. The potential gain is enormous: it aligns the development team with the release schedule. Today, where so much of the workflow can be automated, you only need a one-time setup of your CI/CD pipeline to be able to produce and ship multiple times per day.
One important clarification that will come back often: CI/CD is not a tool, a technology or a programming language. It is a methodology — a set of operating principles that need to be adopted to speed up software development and delivery. Some people new to the topic mistake it for a piece of technology or a language, but it is none of that. CI/CD is just a collection of standards and practices that a team agrees to follow. In essence, it forces a team to deliver code and changes frequently and predictably.
That is a first, simple understanding of what CI/CD really means. In the next video we will look at the individual terms — CI, CD, pipeline, job, stage, runner — one by one. Thanks for watching, see you in the next video.
Summary
This lesson introduces CI/CD (Continuous Integration and Continuous Deployment/Delivery) as a methodology for automating software development and release cycles. CI/CD enables teams to deliver applications faster by automating build, test, and deployment stages, reducing human error and operational costs. The key insight is that CI/CD is not a specific tool or technology, but rather a set of practices and principles that teams must adopt to accelerate development velocity.
Key points
- CI/CD automates development stages (build, test, deploy) to minimize human intervention and errors
- Continuous Deployment allows developers to push code changes directly to production multiple times per day
- CI/CD is a methodology and set of practices, not a specific tool or programming language
- Teams adopting CI/CD must establish standards and workflows for frequent, reliable code delivery
- Automation reduces both production risk and time-to-market for software releases
FAQ
What is the difference between Continuous Integration and Continuous Deployment?
Continuous Integration (CI) is the automated testing and building of code changes. Continuous Deployment (CD) is the automated release of those changes to production. Together, CI/CD creates a complete automated pipeline from code commit to live production.
Is CI/CD a specific tool or technology?
No. CI/CD is a methodology and set of principles. It requires adopting specific practices and standards, but is not tied to any single tool or programming language. GitLab provides tools to implement CI/CD, but the concept itself is platform-agnostic.
What are the main benefits of implementing CI/CD?
CI/CD reduces human error, minimizes operational costs through automation, enables faster release cycles (multiple deployments per day), and improves software quality by automating testing and validation at every stage.