Verify Stage Direction

1. You are here:
2. GitLab Direction
3. Verify Stage Direction

• Overview
  • What is Verify?
  • Vision
    • Verify Stage Categories
      • Continuous Integration (CI)
      • Pipeline Composition
      • GitLab Runner Core
      • Fleet Visibility
      • Code Testing and Coverage
      • Job Artifacts
      • Merge Trains
      • Review Apps
      • Mobile DevOps
      • Component Catalog

Overview

What is Verify?

The Verify Stage is responsible for executing on the market needs for continuous integration.

Continuous integration is a critical practice in modern software development. High-performing software development teams check in code to a shared GitLab repository multiple times daily, leveraging automated and repeatable tests and build workflows to produce secure, functional, and deployment-ready software.

Vision

GitLab CI/CD, a core component of our DevSecOps, platform, is the market-leading enterprise solution for CI/CD workflow automation and orchestration. Our powerful orchestration engine addresses the needs of both software developers and the administrators who manage the critical tooling that empowers high-performing development teams to excel. Our strategy focuses on delivering advanced CI/CD capabilities while providing enterprise-grade solutions that scale with your organizations needs. We believe in making automation accessible to all teams, then delivering advanced capabilities that promote greater efficiency and governance without compromising on security as your DevSecOps maturity grows.

We will execute this vision by:

1. Building a comprehensive component ecosystem that makes advanced CI/CD patterns accessible to all teams through free CI/CD inputs, reusable components, and our CI/CD Catalog, while delivering premium enterprise features for organizations requiring advanced governance, security, and scalability.
2. Continuing developing CI/CD inputs features to address enterprise needs for pipeline input validation, reusability, dynamic parameterization, scalability, self-documenting workflows, and flexibility.
3. Significantly investing in improving the CI/CD Catalog. Key themes include:
   • Enterprise accessibility: Enable self-managed customers to access GitLab.com components with automated synchronization and air-gapped environment support
   • Advanced analytics and visibility: Comprehensive component analytics dashboards for usage insights, version tracking, and lifecycle governance
   • Security and governance: Developer security workflows and administrative controls for component publishing and usage
   • Competitive maturity: Comprehensive user experience improvements, including enhanced search, filtering, and navigation
4. Reimagining a holistic new user experience for CI/CD.
5. Focusing on scalability, quality and reliability so that customers can trust GitLab CI/CD to work as expected when they need it most.

Verify Stage Categories

Continuous Integration (CI)

Streamline your software development lifecycle with continuous, automated building, testing, and deploying of iterative code changes. This ensures the early detection of integration issues, bugs, and security vulnerabilities before deploying to production. This category is at the "complete" level of maturity.

Learn more • Documentation • Direction

Pipeline Composition

Advanced features enable you to edit/compose a highly flexible CI/CD pipeline configuration to boost efficiency across a variety of projects.

Learn more • Documentation • Direction

GitLab Runner Core

GitLab Runner is an application to run the GitLab CI/CD jobs in a pipeline.

Documentation • Direction

Fleet Visibility

Evaluate the status and performance of your runner fleet.

Documentation • Direction

Code Testing and Coverage

Code testing and coverage are important parts of a Continuous Integration framework, ensuring that source code is validated by test suites and individual pipeline components perform as expected. This category is at the "complete" level of maturity.

Documentation • Direction

Job Artifacts

This category focuses on user needs of artifacts which are created as an output of a pipeline or job. This includes both the job’s artifacts, job logs and pipeline artifacts.

Documentation • Direction

Merge Trains

Coordinate frequent merge requests and avoid merge conflicts with Merge Trains, preventing code commits from breaking default and main branches. This category is at the "viable" level of maturity.

Documentation • Direction

Review Apps

Gain access to a live instance of your application for every commit, allowing you and stakeholders to ensure thorough validation and collaboration before changes are merged into the main codebase. This category is at the "viable" level of maturity.

Priority: low • Documentation • Direction

Mobile DevOps

Direction

Component Catalog

A collaborative platform for developers who can easily share, build, and maintain high-quality CI/CD configurations.

Learn more • Documentation • Direction