Get the DevOps platform

To ensure strict code review, you can require a minimum number of users to approve of a merge request before it is able to be merged.

For faster code review, draft multiple comments in a merge request code review, before submitting them together all at once.

Assign Code Owners to files to indicate the team members responsible for code in your project. Code owners are assigned automatically as merge request approvers.

Find bottlenecks in your code review process by understanding how long open merge requests have been in review.

Keep master green. A special pipeline runs on the results of merged code before merging into master to detect changes that may be green on a branch but will fail master when merged.

Full Code Quality reports are available on the pipeline page, showing areas of the codebase that do not meet the organization’s preferred style or standards.

Shorten the feedback cycle and enable stakeholders to provide comments through a form in your review app - which is then automatically added to the related merge request .

Visualize the history and current status of pipelines across projects and groups all in a single dashboard that can be customized for each user.

Visualize how pipelines across projects are linked together, including cross project dependencies.

Reduce pipeline queueing and waiting time with merge trains which allows parallel pipeline execution, with each pipeline building off the merge result of the previous one.

Connect your projects hosted on external services (like GitHub or Bitbucket) and leverage the power of GitLab CI/CD pipelines to build, test, and deploy your applications easily.

Manage the deployments and connection to your Kubernetes clusters in a secure and compliant way, driven by code.

Visualize cross-project environments, track change flow from development to production, track pipeline status and diagnose issues from a single dashboard.

Define custom LICENSE, .gitignore, Dockerfile and .gitlab-ci.yml templates for a Group to make consistency easier.

An overview of all the projects, environments provisioned and the numbers of pods used by each environment in a Kubernetes cluster.

Visualize multiple epics and milestones across time in a roadmap view.

Issue board lists that pull in issues in a given milestone

Assign scoped labels mutually exclusively when they have the same scope.

Assign more than one person to an issue at a time.

Plan and track features and work group level epics that collect issues together. Easily create and assign Issues directly from the Epic itself

Multiple Group Issue Boards, similar to Multiple Project Issue Boards

Promote an issue to epic to continue collaboration at a higher-level work abstraction.

Associate a board with a milestone, labels, an assignee, and a weight

Approval rules ensure that the right people review merge requests by specifying eligible approvers and the minimum number of approvals required for a merge request.

Coordinate the order in which merge requests are merged within the same project and/or across different projects.

Reject new code and commits that don’t comply with company policy.

Guarantee quality and standards of your code by mandating a set number of necessary approvals and predefine a list of specific approvers.

Extend the base functionality of protected branches and choose which users can push or merge to a protected branch.

Specify which person, group, or account is allowed to deploy to a given environment, allowing further protection and safety of sensitive environments.

Group owners can prevent new members from being added to projects within a group.

Users using Geolocation-aware DNS can be transparently directed to the closest server available and access repository data faster.

Fail over in minutes to another data-center.

Maintenance mode allows systems administrators to perform maintenance operations, such as preparing for a scheduled failover, with minimal disruption to end users.

Configure replicated Git storage with automatic failover, strong consistency, and read distribution for improved fault tolerance and performance.

Built for distributed teams, GitLab Geo helps to reduce time to clone and fetch large repos with GitLab Geo - thereby speeding up the user experience for all users regardless of location.

Scale GitLab services across multiple nodes to manage demand and provide redundancy. Determine the optimal architecture for your needs using reference architectures.

Supports distributed teams by running multiple registry instances across several regions and syncing between data centers.

Distribute read-only queries among multiple PostgreSQL database servers and reduce the load on the primary database to increase responsiveness.

Forward your logs to a central system.