2663 terms covering AIOps, DevOps, MLOps, FinOps, observability and cloud-native operations.
Written by AI. Published under human oversight.
Access Tokens
Access Tokens in GitLab are secure credentials that allow applications to authenticate and interact with the GitLab API or repositories, enabling automated processes while protecting user credentials.
Artifact
Files generated as a result of a CI/CD job, such as compiled binaries or documentation. Artifacts are stored within GitLab and can be used in subsequent jobs or downloaded by users.
Artifacts
Artifacts in GitLab are files generated by jobs in a CI/CD pipeline, which can be stored and accessed after the job completes, facilitating the sharing of build results or test reports.
Artifacts Management
The process of storing and sharing files generated during pipeline execution. Artifacts can include build outputs, logs, or test reports. GitLab manages retention policies and access control for these assets.
Audit Events
Audit Events record user and system activities within GitLab for security and compliance monitoring. They provide traceability for actions such as permission changes and configuration updates. This strengthens operational accountability.
Auto DevOps
Auto DevOps is a feature that automates the delivery of applications in GitLab through predefined CI/CD practices, including testing, code quality checks, and deployment strategies, reducing manual configuration efforts.
CI/CD Configuration
The setup of continuous integration and deployment settings in the `.gitlab-ci.yml` file, detailing how pipelines are executed, jobs are defined, and environments are managed.
CI/CD Pipelines
Continuous Integration and Continuous Deployment (CI/CD) Pipelines are automated workflows in GitLab that streamline the process of integrating code changes and deploying applications, ensuring consistent integration and testing.
CI/CD Seconds
CI/CD Seconds is a metric in GitLab that measures the total duration of pipeline runs, allowing teams to analyze performance and optimize their CI/CD workflows based on execution times.
CI/CD Variables
CI/CD Variables store configuration values and secrets used during pipeline execution. They can be scoped to projects, groups, or environments. Secure handling of variables supports secret management and operational flexibility.
Code Owners
Code Owners define responsible individuals or teams for specific files or directories in a repository. Merge requests affecting those areas automatically request their review. This ensures accountability and domain-based code governance.
Code Quality
Metrics and tools available in GitLab that assess the maintainability and complexity of code, helping teams improve code quality through automated analysis.
Code Quality Reports
Code Quality Reports generated in GitLab provide insights into the maintainability of the code, highlighting potential issues or technical debt to improve overall code quality before merging changes.
Commit Status
Commit Status in GitLab reflects the state of a commit in terms of whether it has passed or failed CI/CD tests. It provides visibility into the health of code changes before merging.
Compliance Frameworks
Compliance Frameworks in GitLab define sets of policies and controls applied to projects for regulatory alignment. They enforce standardized workflows and approval rules. This supports governance in regulated industries.
Compliance Pipelines
Compliance Pipelines enforce standardized CI/CD configurations across projects to meet regulatory or organizational policies. They can be centrally managed and inherited by multiple projects. This ensures governance and audit readiness.
Container Registry
GitLab's Container Registry provides a secure, private storage for Docker images associated with projects, facilitating the management and deployment of containerized applications in CI/CD workflows.
Container Scanning
Container Scanning is a security feature in GitLab that scans Docker images for vulnerabilities before deployment, ensuring that containerized applications are secure and compliant with security best practices.
Continuous Deployment (CD)
An extension of Continuous Integration that automatically deploys code changes to production after passing tests. In GitLab, this is facilitated through pipelines and deployment configurations.
Custom CI/CD Variables
Custom CI/CD Variables in GitLab allow users to define environment-specific configurations and sensitive data for use within CI/CD jobs, enhancing flexibility and security.
Default Branch
The Default Branch in a GitLab repository is the base branch where changes are merged by default, often used as the primary development branch, typically 'main' or 'master'.
Dependency Proxy
A caching solution in GitLab that reduces build time and network traffic by caching external dependencies for projects, enhancing CI/CD efficiency.
Deploy Key
A special SSH key used to provide read or write access to a specific repository in GitLab. Deploy keys are commonly used for continuous deployment scenarios.
Directed Acyclic Graph (DAG) Pipelines
DAG Pipelines enable jobs to run based on dependencies rather than sequential stages. This accelerates execution by running independent jobs in parallel. It optimizes resource usage and shortens feedback cycles.
Dynamic Child Pipelines
Dynamic Child Pipelines allow pipelines to generate and trigger downstream pipeline configurations during runtime. This supports modular CI/CD architectures and complex build logic. It improves scalability for monorepos and microservices environments.
Environment
A defined context where code changes are deployed and run, such as development, staging, or production. GitLab allows for multiple environments to facilitate robust testing and deployment strategies.
Environment Management
Environment Management in GitLab enables teams to define and control deployment environments, making it easier to manage various stages of the application lifecycle.
Environment Scopes
Environment Scopes restrict CI/CD variables to specific deployment environments like staging or production. They enhance security by ensuring sensitive values are only exposed where needed. This is critical for controlled configuration management.
Epics
Epics are a way to manage related issues and milestones in GitLab, allowing teams to organize and track large initiatives that encompass multiple tasks and deliverables.
Epics Roadmapping
Epics Roadmapping in GitLab enables teams to organize large initiatives across projects and milestones. It supports agile planning and strategic tracking for complex development programs.
Feature Flags in GitLab
Feature Flags enable controlled rollout of new application functionality without redeploying code. Integrated with GitLab CI/CD, they support canary releases and experimentation. This reduces deployment risk and supports progressive delivery.
GitLab Access Token Management
A security feature for managing personal, project, and group access tokens with granular permissions and expiration policies. It enables secure programmatic access while limiting blast radius of compromised credentials.
GitLab Agent for Kubernetes
A lightweight component deployed on Kubernetes clusters that facilitates bidirectional communication with GitLab for GitOps, cluster monitoring, and security scanning. It eliminates the need to expose cluster API credentials to GitLab.
GitLab Alert Management
A feature for centralizing, deduplicating, and routing alerts from various monitoring tools and data sources. It integrates with incident management to automatically create incidents from critical alerts.
GitLab Artifact Management
The system for storing and managing build outputs, binaries, and test reports generated during CI/CD pipeline execution. Artifacts can be preserved for deployment, debugging, or compliance purposes with configurable retention policies.
GitLab Audit Events
Logs that track user actions and configuration changes within GitLab. Audit events support compliance, security monitoring, and forensic analysis. They are essential in regulated or high-security environments.
GitLab Audit Logging
Comprehensive logging of all administrative actions, API calls, and security-relevant events within GitLab. Audit logs provide compliance evidence and enable forensic investigation of security incidents.
GitLab Auto DevOps
Auto DevOps is a GitLab feature that automatically configures CI/CD pipelines with best-practice templates for building, testing, and deploying applications. It leverages Kubernetes and predefined configurations to simplify cloud-native deployments. This approach reduces setup time for modern application delivery.
GitLab CI/CD
GitLab's built-in Continuous Integration and Continuous Deployment (CI/CD) features facilitate automated testing and deployment of code changes. This allows teams to integrate changes more frequently and deliver applications consistently.
GitLab CI/CD Pipeline
A GitLab CI/CD pipeline is an automated workflow defined in a .gitlab-ci.yml file that builds, tests, and deploys code. It consists of stages and jobs executed by GitLab Runners. Pipelines enable continuous integration, delivery, and deployment within a single DevOps platform.
GitLab Compliance Framework
A governance system for enforcing compliance policies across projects, including audit logs, approval requirements, and policy enforcement. It helps organizations meet regulatory requirements like SOC2, HIPAA, and ISO standards.
GitLab Container Registry
The GitLab Container Registry is a built-in Docker registry integrated with GitLab projects. It allows storing and managing container images alongside source code. This simplifies CI/CD-based container workflows.
GitLab DAST Scanning
Dynamic Application Security Testing that evaluates running applications for security vulnerabilities by simulating attacks. DAST runs as part of the deployment pipeline to catch runtime security issues.
GitLab Dependency Proxy
The GitLab Dependency Proxy caches external container images locally to reduce dependency on public registries. It improves pipeline reliability, performance, and network efficiency.
GitLab Dependency Scanning
An automated security feature that analyzes project dependencies for known vulnerabilities in libraries and packages. It generates reports highlighting outdated or compromised dependencies that require updates.
GitLab Deployment Approvals
A workflow control feature requiring designated approvers to authorize deployments to critical environments. It adds a manual gate in the deployment pipeline to prevent unauthorized or unreviewed releases.
GitLab Environment
An Environment in GitLab represents a deployable target such as development, staging, or production. It tracks deployment history and application status. Environments enable visibility and control over release promotion processes.
GitLab Environment Tracking
A feature that monitors and tracks deployed application instances across different environments, showing deployment history and current state. It provides visibility into which versions are running in production, staging, and development.
GitLab Error Tracking
An integrated error monitoring feature that aggregates application exceptions and errors reported through SDKs or APIs. It helps development teams identify and prioritize critical issues in production applications.
GitLab Feature Flags
A mechanism for enabling or disabling application features without redeploying code. Feature flags integrate with GitLab deployments for controlled rollouts. They support experimentation and risk mitigation strategies.
GitLab Flow
GitLab Flow is a branching and release strategy that integrates feature-driven development with environment-based deployments. It combines feature branches with long-lived environment branches such as production or staging. This workflow simplifies release management across teams.
GitLab GitOps Workflow
A declarative infrastructure and application deployment methodology where Git serves as the source of truth for desired system state. Changes flow through Git-based workflows enabling version control and rollback capabilities for all infrastructure changes.
GitLab Group-Level Protection
Security policies applied at the group level that cascade to all projects within the group, enforcing consistent security standards. It includes approval requirements, protected branch rules, and IP allowlisting.
GitLab Incident Management
A built-in module for creating, tracking, and managing incidents directly within the GitLab platform. It links incidents to issues, merge requests, and runbooks to facilitate coordinated incident response.
GitLab Infrastructure as Code (IaC) Scanning
Security scanning that detects misconfigurations and compliance violations in Infrastructure as Code files like Terraform and CloudFormation. It ensures cloud resources are deployed with proper security controls.
GitLab Issue Boards
Kanban-style boards used to manage and visualize issues within projects. They support workflow customization with labels and milestones. Issue Boards enhance Agile project management within GitLab.
GitLab Kubernetes Agent
The GitLab Kubernetes Agent enables secure, pull-based communication between GitLab and Kubernetes clusters. It supports GitOps workflows and cluster management directly from GitLab. This replaces legacy certificate-based integrations.
GitLab Kubernetes Integration
Native connectivity between GitLab and Kubernetes clusters enabling automated deployment, monitoring, and management of applications. It supports GitOps workflows where the Git repository serves as the single source of truth for cluster state.
GitLab License Compliance
A feature that scans project dependencies to identify their licenses and ensures compliance with organizational policies. It prevents the use of incompatible open-source licenses in production software.
GitLab Metrics Dashboards
Customizable dashboards within GitLab that visualize application and infrastructure metrics from connected monitoring systems. They enable teams to correlate deployments with performance changes.
GitLab On-Call Scheduling
An integrated on-call management feature for creating schedules, escalation policies, and alert routing. It enables seamless integration with incident management and alerting systems.
GitLab Package Registry
The GitLab Package Registry provides storage for software packages such as Maven, npm, PyPI, and NuGet. It integrates directly with CI/CD pipelines for publishing and retrieving artifacts. This supports unified artifact management within GitLab.
GitLab Pages
GitLab Pages is a feature that allows users to host static websites directly from a repository, enabling developers to share documentation, portfolios, or project sites directly tied to their codebase.
GitLab Runner
A GitLab Runner is an application that processes builds and applications by executing jobs specified in a CI/CD pipeline, allowing for distributed and concurrent execution on various platforms.
GitLab SAST Scanning
Static Application Security Testing integrated into GitLab pipelines that analyzes source code for vulnerabilities without execution. It identifies common security issues early in the development lifecycle.
GitLab Secret Detection
A security scanning mechanism that identifies hardcoded secrets, API keys, and credentials in repositories before they are exposed. It prevents accidental leakage of sensitive information into version control.
GitLab Secure Scanning
GitLab Secure Scanning integrates security testing into CI/CD pipelines, including SAST, DAST, dependency scanning, and container scanning. It shifts security left by identifying vulnerabilities early in development. Findings are consolidated within merge requests and dashboards.
GitLab Service Mesh Integration
Integration capabilities allowing GitLab to visualize and manage service mesh traffic policies, security policies, and observability across microservices. It provides GitOps-driven control of service mesh configurations.
GitLab Status Page
A customizable public-facing status page that displays system health, ongoing incidents, and maintenance schedules. It automatically updates based on incidents created in GitLab, keeping stakeholders informed in real-time.
GitLab Webhooks
HTTP callbacks triggered by events such as pushes, merges, or pipeline completions. Webhooks enable integration with external systems like monitoring tools or chat platforms. They support event-driven automation workflows.
GitOps Deployment Workflow
GitOps Deployment Workflow in GitLab uses Git repositories as the source of truth for infrastructure and application deployment states. Changes are automatically synchronized to target environments through declarative configurations.
GitOps with GitLab
GitOps with GitLab uses Git repositories as the single source of truth for infrastructure and application deployments. Changes are automatically synchronized to target environments through CI/CD or Kubernetes agents. This approach enhances auditability and rollback capabilities.
Golang Integration
Golang Integration in GitLab supports the building and testing of applications written in Go, optimizing the CI/CD process specifically for Go ecosystems and libraries.
GraphQL API
A flexible API offered by GitLab that allows developers to query and manipulate GitLab resources with precise control over the returned data, enhancing integration capabilities.
Group Access Tokens
Group Access Tokens provide scoped authentication for automation and integrations across GitLab groups. They simplify credential management for shared operational tasks.
Group-level CI/CD Variables
Group-level CI/CD Variables allow shared configuration values across multiple projects within a GitLab group. They reduce duplication and centralize secret management. Access can be scoped and protected for security.
Group-level Epics
Group-level Epics provide a way to manage large initiatives that span multiple projects within a GitLab group. They aggregate related issues and track progress at a strategic level. This enhances portfolio visibility and planning.
Group-Level Permissions
Group-Level Permissions in GitLab establish access controls across multiple related projects within a group, streamlining user management and security across a team's repositories.
Infrastructure as Code (IaC) Scanning
IaC Scanning in GitLab analyzes infrastructure definitions like Terraform or CloudFormation for security and compliance issues. It runs during CI/CD pipelines to catch misconfigurations early. This reduces infrastructure-related risks before deployment.
Instance-Level CI Templates
Instance-Level CI Templates provide reusable CI/CD configurations shared across multiple projects in a GitLab environment. They promote consistency and reduce duplicated pipeline logic.
Instance-Level Settings
Administrative configurations that apply across an entire GitLab installation. These settings govern authentication, storage, security policies, and integrations. Instance-level controls are critical for enterprise deployments.
Instance-level Templates
Instance-level Templates allow administrators to define standardized project templates across a GitLab instance. These templates can include CI/CD configurations and project settings. They accelerate onboarding and enforce best practices.
Issue Board
GitLab's Issue Board is a visual representation of issues that can be organized using lists, representing workflows. It simplifies project management and tracking within GitLab.
Issue Boards
Issue Boards in GitLab are visual project management tools that help teams track and manage their issues and tasks using a Kanban-style interface, enhancing workflow visualization and collaboration.
Issues
Trackable elements for managing tasks, bugs, or features within a GitLab project. Issues provide a centralized system for collaboration, task assignment, and progress monitoring.
Iterations
Iterations in GitLab define time-boxed development cycles similar to sprints. Issues can be assigned to iterations for structured planning and tracking. This supports Agile delivery methodologies.
License Compliance Scanning
License Compliance Scanning identifies open-source software licenses used in dependencies and checks them against organizational policies. This helps reduce legal and compliance risks in software distribution.
Manual Jobs
CI/CD jobs that require human intervention before execution. They are often used for production deployments or approval gates. Manual jobs add governance and control to automated pipelines.
Merge Request
A request to merge code changes from one branch into another in GitLab, allowing for review and discussion before integration. It serves as a central place for collaboration on code modifications.
Merge Request Approval Rules
Approval Rules in GitLab can be established for merge requests, specifying the criteria needed for a merge request to be approved, which helps maintain code quality and adherence to team standards.
Merge Request (MR)
A Merge Request is a collaboration mechanism in GitLab used to propose and review code changes before merging into a target branch. It supports code review, discussions, approvals, and pipeline validation. MRs enforce governance and improve code quality.
Merge Request Review
A Merge Request Review is the process where team members examine code changes proposed in a merge request, providing feedback and approving or requesting modifications before the changes are merged into the primary codebase.
Merge Request Widgets
Merge Request Widgets display contextual information such as pipeline status, security findings, and deployment results directly within merge requests. They improve developer visibility into code quality and operational readiness.
Merge Request Workflow
A GitLab feature enabling code review and collaboration before integrating changes into the main branch. Merge requests support discussions, approvals, and automated checks to maintain code quality standards.
Merge Train
A feature in GitLab that queues merge requests to ensure orderly integration into the main branch, preventing conflicts and ensuring automated tests are run.
Merge Trains
Merge Trains ensure that multiple merge requests are validated sequentially in a queue before merging into the main branch. Each MR is tested with the changes from earlier queued MRs. This prevents broken builds and maintains branch stability.
Monitoring Dashboard
A visual representation in GitLab that provides real-time insights into application performance and CI/CD pipelines, aiding in decision-making and performance assessment.
Multi-project Pipelines
Multi-project Pipelines coordinate CI/CD workflows across different GitLab projects. A pipeline in one repository can trigger pipelines in another. This supports microservices architectures and cross-repository dependencies.
Parent-Child Pipelines
Parent-Child Pipelines enable modular pipeline design by allowing a parent pipeline to trigger multiple child pipelines. This improves maintainability and scalability for complex workflows. It supports large monorepos and microservices architectures.
Pipeline
A CI/CD Pipeline in GitLab is an automated process that defines the stages a project goes through from code commit to deployment. It allows for testing, building, and deploying code seamlessly.