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 - Cycle Analytics
Description
Cycle Analytics specifies how much time taken by the team to complete the each stage in their workflow and allows GitLab to store data of development efforts in one central data store.
The cycle analytics page can be found under the Overview section.
Step 1 − Login to your GitLab account and go to your project −
Step 2 − Cpck on the Cycle Analytics option under Overview tab which will open the screen as shown below −
The cycle analytics contains following stages −
Issue − It specifies how much time taken to solve an issue.
Plan − It specifies the time between pushing first commit to branch and action took for previous stage.
Code − It specifies the time between pushing first commit to branch and created merge request for that commit.
Test − It specifies how much time need to GitLab CI/CD to test the code.
Review − It specifies time taken to review the merge request.
Staging − It defines the time spent between merging and deploying to production.
Production − It specifies the time taken to complete the entire process, from creating an issue to deploying code to production.