GitLab Basics
- GitLab - Squashing Commits
- GitLab - Rebase Operation
- GitLab - Add a File
- GitLab - Create a Branch
- GitLab - Fork a Project
- GitLab - Create Project
- GitLab - SSH Key Setup
- GitLab - Git Commands
- GitLab - Installation
- GitLab - Introduction
GitLab Users and Groups
GitLab Issue Tracker
- GitLab - Wiki Pages
- GitLab - Milestones
- GitLab - Referencing Issues
- GitLab - Merge Requests
- GitLab - Create Issue
GitLab Instance Management
GitLab Continuous Integration
- GitLab CI - Container Registry
- GitLab CI - Cycle Analytics
- GitLab CI - Advanced usage of CI
- Configuring GitLab Runners
- GitLab CI - Permissions
- GitLab - CI/CD Variables
- GitLab - CI/CD
- GitLab CI - Introduction
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
GitLab - CI/CD
Description
GitLab CI (Continuous Integration) service is a part of GitLab that build and test the software whenever developer pushes code to apppcation. GitLab CD (Continuous Deployment) is a software service that places the changes of every code in the production which results in every day deployment of production.
The following points describe usage of GitLab CI/CD −
It is easy to learn, use and scalable.
It is faster system which can be used for code deployment and development.
You can execute the jobs faster by setting up your own runner (it is an apppcation that processes the builds) with all dependencies which are pre-installed.
GitLab CI solutions are economical and secure which are very flexible in costs as much as machine used to run it.
It allows the project team members to integrate their work daily, so that the integration errors can be identified easily by an automated build.