Feature trailActive

Container Virtual Registry

GitLab Container Registry is evolving to support a Container Virtual Registry, which acts as a single endpoint to pull from multiple upstream container sources with built-in caching. This feature aims to reduce operational overhead, improve pipeline reliability, and centralize image management for organizations using multiple registries. It supports upstream registries with long-lived token authentication and pull-through caching, with future plans to include cloud provider registries requiring

22 posts · 2016–2026

Timeline

…20172026

Feature trailActive

Performance Optimization

GitLab CI/CD pipelines offer fine-grained permissions for job tokens, moving from Beta to General Availability. This enhancement allows maintainers to implement granular access controls for job tokens to API resources, adhering to the principle of least privilege. The initial release supports permissions for repositories, deployments, environments, jobs, packages, pipelines, releases, secure files, and Terraform state. This feature aims to reduce the attack surface, eliminate reliance on lon. This post details implementing continuous deployment with GitLab, focusing on artifact management strategies (versioning, retention, registry access), environment strategy, and deployment targets. It provides a step-by-step example for containerizing a simple HTML application, setting up a CI/CD pipeline with Docker, publishing to the GitLab Container Registry, and deploying to a virtual machine using SSH authentication. The pipeline includes stages for publishing, staging, and production deployments, with environment configuration for tracking.

70 posts · 2015–2026

Timeline

…20172026

Feature trailActive

On-Premises Deployment Considerations

GitLab 19.0 introduces significant changes to its deployment and dependency management for self-managed instances. Key updates include the replacement of NGINX Ingress with Gateway API and Envoy Gateway as the default networking component, and the removal of bundled PostgreSQL, Redis, and MinIO from the Helm chart. Support for PostgreSQL 16 is dropped in favor of PostgreSQL 17 as the minimum requirement. Additionally, support for Ubuntu 20.04 and Redis 6 is discontinued. The `heroku/builder:24` image replaces `heroku/builder:22` in Auto DevOps, and bundled Mattermost is removed from the Linux package. Support for SUSE distributions is also discontinued. These changes necessitate proactive migration and configuration updates for self-managed deployments to ensure compatibility and continued support.

45 posts · 2015–2026

Timeline

…20172026

Feature trailActive

DevOps Platform Total Cost of Ownership Modeling

GitLab is evolving its approach to help customers understand and manage the Total Cost of Ownership (TCO) of their DevOps platform. This includes providing detailed breakdowns of cost categories such as platform access, CI/CD consumption, AI usage, runner infrastructure, security and compliance tools, additional tools, support and services, internal operations, and migration/change costs. The goal is to enable transparency for stakeholders, identify cost drivers, and facilitate informed decision-making. This post details a worksheet for estimating annual TCO, emphasizing the importance of modeling cost drivers independently and considering the hidden costs of tool sprawl. It also provides best practices for reducing platform TCO, such as right-sizing licenses, eliminating unnecessary CI/CD work, and building flexibility into AI spend.

2 posts · 2019–2026

Timeline

20192026

Feature trailActive

Community Growth and Contribution Milestones

GitLab has improved its open source community growth and contribution milestones by developing and implementing a semi-automated onboarding solution. This solution leverages GitLab's own tools, including issue templates, scheduled pipelines, webhooks, GLQL, and project mirroring, to streamline the contributor journey. Key enhancements include personalized onboarding issues, standardized responses via comment templates, immediate pipeline triggers for access requests, automated nudges, and the integration of new features like Scala language support for Orbit and GitLab Duo, instance-level enforcement for Secret Push Protection, configurable merge train pipeline limits, supported-platform details for container image indexes, and improved screen reader context for documentation pages. The platform also introduced new predefined variables (`CI_TRACEPARENT`, `CI_TRACESTATE`) for W3C Trace Context in CI/CD jobs, enabling better correlation across pipelines and distributed systems. The User Applications REST API and Token Information API have been enhanced for programmatic management of OAuth applications and SCIM tokens, respectively, improving automation around token inventory and governance.

5 posts · 2022–2026

Timeline

20222026

Feature trailActive

Custom Compliance Frameworks

GitLab's DevSecOps platform integrates with HackerOne to streamline vulnerability management. Security researchers' findings are automatically converted into GitLab issues, enabling development teams to address them within their existing workflow. This bi-directional sync improves alignment between development and security teams, accelerates remediation, and enhances security visibility. GitLab also offers built-in security scanning tools like SAST, DAST, and dependency scanning, which can be in

40 posts · 2019–2026

Timeline

20192026

Feature trailActive

GitLab CI and Distributed Builds

GitLab CI/CD is continuously evolving to enhance automation, security, and efficiency in software delivery. This includes best practices for pipeline implementation, advanced strategies like AI-assisted pipeline generation, and migration guides. The focus remains on enabling teams to develop and deliver software in an agile, automated, and efficient manner, with a strong emphasis on security and compliance throughout the pipeline.

287 posts · 2013–2026

Timeline

…20172026

Feature trailActive

AI Data Usage and Privacy Controls

GitLab Duo Agent Platform enhances DataOps by automating dbt model generation, including source and workspace models, complete with configurations, tests, and documentation. This significantly reduces manual effort and time for data engineers. The platform is exploring direct integrations with data platforms like Snowflake via Model Context Protocol (MCP) to further automate data structure understanding and model generation. Quality validation is integrated through CI pipelines and AI-generated test queries.

7 posts · 2021–2026

Timeline

20212026

Feature trailActive

GitLab is developing a native secrets manager to simplify secret management across the DevSecOps platform. The initial release will focus on CI workflows, with plans to expand to all GitLab workflows. It will support an open-source secrets manager (OpenBao) and integrate with existing security capabilities like secret detection, access token management, compliance audit logging, and secured artifacts. The goal is to reduce complexity, lower risk, and provide a centralized, cloud-agnostic solution, while continuing to support third-party integrations.

17 posts · 2018–2026

Timeline

20182026

Feature trailActive

Code Review Workflow

GitLab is enhancing its code review process by integrating automated reviewer suggestions directly into merge requests using a machine learning algorithm that analyzes the changes in an MR and a project's contribution graph. This evolution moves away from a separate Slack-based tool, addressing workflow friction and availability issues. The goal is to ensure more even distribution of reviews, prevent knowledge silos, and improve the efficiency of the review process by making it an integral part of the workflow. This post introduces GitLab Duo with Amazon Q, an agentic AI solution that performs comprehensive code reviews, analyzes code changes, and provides actionable feedback on bug detection, readability, syntax errors, and adherence to coding standards.

30 posts · 2015–2026

Timeline

…20172026

Feature trailActive

Browser-based DAST Analyzer

GitLab DAST continues to evolve, with this post detailing its comprehensive capabilities, including runtime vulnerability detection, seamless CI/CD integration for shift-left security, and compliance assurance. It elaborates on passive vs. active scanning methodologies and provides detailed guidance on authentication configuration for achieving complete security coverage. The post also highlights the Tanuki Shop demo application as a practical example of DAST implementation within CI/CD pipelines.

13 posts · 2019–2026

Timeline

20192026

Feature trailActive

DevSecOps Platform Evolution

GitLab's DevSecOps platform continues to evolve, integrating security throughout the software development lifecycle. This includes addressing the complexities of software supply chain security beyond traditional dependency scanning, encompassing source, build, artifact, deployment, and tool security. The platform is also adapting to the emerging risks introduced by AI, such as model supply chain attacks and insecure AI-generated code. Key efforts focus on bridging the gap between developer velocity and security, with recent advancements including secure package publishing with signing and attestation using Sigstore's Cosign, and automated vulnerability scanning.

9 posts · 2018–2026

Timeline

20182026

Feature trailActive

FIPS Package Dependency Management

GitLab enhances its DevSecOps platform with AI/ML capabilities, including the introduction of GPU-enabled runners on GitLab.com. These runners accelerate ModelOps and HPC workloads, such as training and deploying large language models (LLMs). The post details how to use these runners, including selecting appropriate Docker images with NVIDIA CUDA drivers and verifying GPU functionality. It provides examples for Python model training and scientific simulations, and a more advanced example of AI-assisted development. Additionally, FIPS packages are evolving to use distribution-provided curl and OpenSSL for improved security and maintainability, shifting responsibility for curl security updates to the customer.

28 posts · 2019–2026

Timeline

20192026

Feature trailActive

CI/CD Carbon Measurement

GitLab CI/CD is enhanced to integrate carbon measurement tools like Eco CI and Carmen. These tools provide visibility into the energy consumption and carbon emissions of CI/CD jobs and infrastructure components. This enables engineers to identify resource-intensive jobs, track emissions trends, and make data-driven decisions to reduce their environmental impact. The integration aims to make carbon footprint a measurable aspect of DevOps practices, aligning with growing sustainability expectations and regulations.

1 post · 2026

Timeline

Feature trailActive

Log Management and Observability

GitLab's observability capability is open-sourced and relies on open APIs like Prometheus and OpenTelemetry. It is built into the GitLab DevOps platform to help users use the capability right away within their native workflow. The vision is to make every GitLab project observable by default, with features that are easy to operate without specialized, expert skills. Teams can connect the dots between ever-changing systems and their impact on user experience. This post introduces Distributed Tracing, which allows engineers to identify the source of application performance issues by analyzing the timing of each operation and any errors as they occur. Traces are composed of spans, representing individual operations, and are particularly valuable for microservices architectures. Data is collected using OpenTelemetry, ingested and retained at scale with ClickHouse and Kubernetes, and analyzed through an advanced user interface including a Trace Explorer with filtering, error highlighting, RED metrics, and a timeline view. GitLab engineers are using Distributed Tracing to debug issues in the GitLab Agent for Kubernetes and optimize build pipeline duration by identifying performance bottlenecks.

38 posts · 2014–2026

Timeline

…20172026

Feature trailActive

GitLab.com Pricing and Monetization Strategy

GitLab is evolving its seat control features to provide more predictable costs and prevent unexpected overages. Recent improvements to restricted access enhance its integration with identity providers (SAML, SCIM, LDAP, OIDC), allowing users to be provisioned with a non-billable Minimal Access role when no paid seats are available. Dormant users are now placed in a pending approval state instead of being silently reactivated, preventing silent overages. Clearer warnings, banners, and notifications are provided to administrators and group owners.

13 posts · 2014–2026

Timeline

…20172026

Feature trailActive

Bug Triage and Reporting

GitLab has established a structured approach to handling bugs, differentiating between security, regression, and feature bugs. This system aims to prioritize fixes based on severity and impact, encouraging community contributions for identification and resolution. The process involves clear channels for reporting different bug types, from direct contact for security vulnerabilities to the issue tracker and feedback channels for other bugs. This framework is crucial for maintaining the stability and reliability of the platform.

36 posts · 2014–2026

Timeline

…20172026

Feature trailActive

Issue Tracking and Merge Request Workflow Integration

GitLab's Agile planning capabilities are enhanced to support SAFe ceremonies by mapping SAFe concepts (Epic, Capability, Feature, User Story, Task, Team, Sprint, PI) to GitLab's work item hierarchy (Epics, Issues, Tasks) and organizational structure (Groups, Subgroups, Projects). This allows for end-to-end traceability from strategy to execution within a single DevSecOps platform. PI Planning is supported through Roadmap and Epic boards, Refinement via Epic boards and drawer views, Sprint Planni. The new epic experience introduces assignees, health status, time tracking, ancestry view, condensed descriptions, and custom colors for epics. It is built on a unified Work Items framework for consistency across epics, issues, and tasks, and future plans include templates, custom fields, configurable statuses, project-level epics, cloning, moving between groups/projects, and milestones.

65 posts · 2015–2026

Timeline

…20172026

Feature trailActive

GitLab Installation and Updates

GitLab's installation and update processes are continuously refined to support a wider range of hardware and operating system configurations. This includes efforts to enable official support for ARM64 architectures and provide optimized installation methods for platforms like Raspberry Pi OS, even when official support is still in development. The omnibus-gitlab package is the primary method for installation. This post details a migration of the package hosting system for `packages.gitlab.com` to extend the Omnibus package signing key expiration to 2025, ensuring continued integrity checks for package distribution.

47 posts · 2014–2026

Timeline

…20172026

Feature trailActive

GitLab Serverless

GitLab is decomposing its monolithic PostgreSQL database into independent databases, starting with the separation of CI-related data. This involved extensive planning, proof-of-concept work, and the development of tools and documentation to manage cross-database dependencies, such as cross-join detection, cross-database transaction detection, and loose foreign keys. The project leveraged Rails' multi-database support and addressed challenges like mirroring data. This post details a major version of this decomposition, specifically the general availability of Gitaly on Kubernetes, allowing for a fully Kubernetes-native GitLab deployment and consolidation of infrastructure by moving Gitaly into the cluster. This eliminates the need to maintain and monitor a separate VM fleet alongside Kubernetes nodes.

2 posts · 2018–2026

Timeline

20182026

Feature trailActive

High Availability

GitLab Geo is evolving its replication framework to enable teams across GitLab to add new data types with reduced duplication and effort. This includes a new Replicator class and Replicator strategy concept for blobs and Git repositories, and a more flexible event system. The goal is to minimize lag time for Geo support, increase awareness in other teams, and influence the planning of new features to be Geo-friendly from the start. Initial implementation focused on replicating new Package files. GitLab now backs its 99.9% availability commitment with service credits for Ultimate customers on GitLab.com and GitLab Dedicated. When monthly availability falls below this threshold, eligible customers receive credits toward future invoices. This commitment ensures your DevSecOps workflows have the reliability they need.

17 posts · 2013–2026

Timeline

…20172026

Feature trailActive

SAML Single Sign-On (SSO) Integration

GitLab continues to enhance its authentication and authorization capabilities, with a significant focus on integrating with enterprise identity management systems. This includes the ongoing development and refinement of SAML (Security Assertion Markup Language) support for Single Sign-On (SSO), and the integration with SCIM for automated user provisioning and deprovisioning. This post details the practical implementation of SAML and SCIM with Google Workspace, providing step-by-step guidance on configuring group synchronization for automatic role mapping.

15 posts · 2014–2026

Timeline

…20172026

Feature trailActive

AI Data Usage and Privacy Controls

GitLab's approach to AI data usage and privacy is to not collect or train on customer data, regardless of subscription tier. This contrasts with Atlassian's new policy to collect metadata and in-app content by default for AI training, with opt-out only available for Enterprise customers. GitLab emphasizes unconditional data commitments, transparency, auditability, and separation of customer data from vendor AI training. For organizations requiring on-premises AI processing, GitLab Duo Agent Platform is available with Self-Managed deployments, allowing integration with self-hosted AI models where prompts and code never leave the customer's environment. GitLab also provides IP indemnification for Duo-generated output.

1 post · 2026

Timeline

Feature trailActive

IDE Attack Prevention

GitLab's Security Operations team has developed custom controls to detect and prevent malware campaigns that leverage IDE tasks for distribution, specifically addressing the 'Contagious Interview' threat campaign. This involves low-level detection mechanisms focusing on subprocess execution within IDEs like VS Code, aiming to protect GitLab workstations and customers from malicious code execution that can lead to infostealers, credential theft, and persistence establishment. The detection leverages custom scripts to decode malware from binary data in a fake font file, and abuses legitimate services like Vercel to host payloads. The team also identified and banned accounts used for these campaigns, and observed distinct subgroups of activity operating in parallel.

6 posts · 2021–2026

Timeline

20212026

Feature trailActive

Test Result Upload Automation

GitLab CI/CD capabilities are enhanced with automated test result uploads from pipelines to external test management platforms like QMetry, enabling end-to-end traceability, faster feedback loops, and compliance adherence. This builds upon existing CI/CD features for running tests and generating reports. The integration of Hurl allows for continuous testing of web apps and APIs directly within GitLab CI/CD jobs, enabling automated HTTP request testing, response assertion, and integration with cu

7 posts · 2018–2026

Timeline

20182026

Feature trailActive

GitLab Feature Flags

GitLab's feature flags capability, integrated with the Unleash SDK, allows for decoupling deployment from release. This tutorial demonstrates how to use the Unleash Python SDK to connect to GitLab's Unleash-compatible API for real-time control of feature flags in a Flask application. It covers setting up flags, understanding strategies (like percent rollout and user IDs), obtaining credentials, integrating the SDK, and checking flag status locally for immediate application behavior changes without network calls per check. The integration uses a project-specific Instance ID for read-only access to flag state.

4 posts · 2019–2026

Timeline

20192026

Feature trailActive

Issue and Merge Request Workflow Enhancements

GitLab's Agile planning experience is unified under a 'Work Items' framework, consolidating epics, issues, and other work item types into a single list view. This framework is designed to provide a consistent user experience, enable deeper planning capabilities like hierarchy views and consolidated boards, and allow for customizable work item types. Saved views enable users to store and reuse customized list configurations for efficient reporting and consistent team workflows. This evolution aims to provide a more powerful, flexible, and user-friendly Agile planning experience by unifying issues and epics, and paving the way for new planning object types. Tasks have been introduced as the first work item type to leverage this framework, providing valuable feedback for future iterations.

33 posts · 2014–2026

Timeline

…20172026

Feature trailActive

Exact Code Search

GitLab's Exact Code Search, powered by Zoekt, provides lightning-fast, precise code searching across massive codebases (48TB+). It offers Exact Match mode for zero false positives, Regular Expression mode for complex pattern matching, and multi-line results for contextual understanding. The system is built on a distributed, self-registering node architecture with intelligent load balancing and seamless integration with GitLab's permission system, enabling rapid debugging, code exploration, refactoring, and security auditing.

1 post · 2019–2026

Timeline

20192026

Feature trailActive

SSH Key Management and Authentication

GitLab has focused on simplifying user authentication and access management. This includes enhancing SSH key usage by providing screencasts to demonstrate ease of use and introducing an alternate `git+ssh` port (443) on GitLab.com to circumvent network restrictions. This post details a coordinated effort with Yubico to integrate hardware security keys (YubiKeys) for two-factor authentication, enhancing security beyond SMS or push notifications by leveraging the U2F protocol for phishing and Man-in-the-Middle attack resistance. Passkeys are now available for passwordless sign-in or as a phishing-resistant two-factor authentication (2FA) method, utilizing WebAuthn technology and public-key cryptography. They work across desktop browsers, mobile devices, and FIDO2 hardware security keys.

14 posts · 2016–2026

Timeline

…20172026

Feature trailActive

Documentation Localization Infrastructure

GitLab is evolving its approach to documentation management by adopting a comprehensive 'docs-as-code' workflow. This involves using GitLab itself for planning, creating, reviewing, editing, and publishing documentation. The process leverages GitLab issues and issue boards for planning, merge requests for collaborative feedback and review, and a review app feature for previewing changes. Automated testing is integrated into the CI/CD pipeline to ensure content quality, and the final HTML output is dynamically generated using Hugo. This infrastructure is now being extended to support localization, starting with Japanese, by integrating new folders within the existing English content structure (`doc-locale/ja-jp`). This architecture keeps translations alongside source content, enabling version control, collaborative review, and automated quality checks. An AI-assisted translation workflow with human post-editing is employed, balancing speed and quality. Technical challenges include preserving complex markdown syntax, establishing English fallback mechanisms, dynamically adjusting navigation and linking with anchor IDs, and extending CI/CD pipelines for localized content testing. A centralized translation request system orchestrates the workflow, monitors English files, routes for translation, and creates translation merge requests. Future priorities include enhancing search experience for localized users and accelerating the continuous localization workflow.

5 posts · 2016–2025

Timeline

…20172026

Feature trailActive

Project Hosting and Collaboration Alternatives

GitLab's integration management capabilities are evolving to streamline the connection of third-party applications with GitLab projects. Previously, integrations were managed only at the project level, requiring repetitive configuration for each project. The introduction of group-level integration management allows for simultaneous configuration of integrations across all projects within a group, saving significant administrative time and effort. This feature also enhances security by enabling better control over access and permissions. This post details the benefits of consolidating to a single tool for improved collaboration, security, and administrative overhead reduction, highlighting GitLab Enterprise Edition's capabilities for project sharing and permission management.

23 posts · 2014–2025

Timeline

…20172026

Feature trailActive

DevOps Platform Evolution

GitLab's DevOps platform is being extended to support mainframe development environments through a partnership with IBM. This involves providing native z/OS Runner support for CI/CD pipelines that execute directly on IBM z/OS infrastructure. The solution aims to unify source code management by replacing legacy library managers with GitLab's repository system, and integrates with IBM Developer for z/OS Enterprise Edition (IDzEE) for dependency-based builds, automated code scanning, and debugging. This enables end-to-end visibility across mainframe and distributed environments, facilitating incremental modernization and hybrid cloud strategies.

80 posts · 2014–2025

Timeline

…20172026

Feature trailActive

Kubernetes Terminology and Concepts

1 post · 2024

Timeline

20242026

Feature trailQuiet since 2024

…20172026

Feature trailQuiet since 2021

CI/CD Minute Quotas and Abuse Prevention

GitLab.com is extending CI/CD minute usage quotas to public projects not part of GitLab open source programs to prevent abuse, such as cryptocurrency mining, which negatively impacts performance and availability of shared runners. This change aims to ensure reliable service for all users by limiting excessive consumption of free pipeline minutes. Users will be notified upon reaching their quota and can upgrade their plan or purchase additional minutes. Self-managed users and members of GitLab's open source programs are unaffected.

6 posts · 2020–2021

Timeline

20202026

Feature trailQuiet since 2021

User-centric GitLab Navigation

GitLab is exploring user-centric navigation patterns beyond the traditional project-centric model. This includes developing standalone applications like GitDock to test new ideas and gather learnings for improving the main GitLab start page and other navigation features. The goal is to provide a more personalized and efficient way for users to access relevant information and activities.

1 post · 2021

Timeline

20212026

Feature trailQuiet since 2021

Markdown Rendering and Flavored Markdown

GitLab's Markdown rendering has evolved to align with established specifications, requiring two spaces at the end of a line for a newline. The Web IDE and Web Editor now include a real-time, side-by-side preview panel for Markdown content, allowing users to see changes as they are made without context switching.

5 posts · 2014–2021

Timeline

…20172026

Feature trailQuiet since 2021

Markdown Rendering Behavior

GitLab has evolved its Markdown rendering to align with the CommonMark specification, ensuring consistent rendering across the platform. This involved a phased migration from RedCarpet to CommonMark, first for new content and then for repository and wiki files. The process included driving upstream changes to libraries like cmark-gfm and commonmarker to address specific rendering behaviors and bugs. The goal is to provide a more predictable and reliable user experience for all Markdown content. This post details the change to require two spaces at the end of a line for a newline, aligning with the Markdown specification and applying this behavior to descriptions and comments in issues and merge requests.

2 posts · 2014–2021

Timeline

…20172026

Feature trailQuiet since 2021

Spamcheck Anti-Abuse Engine

GitLab is introducing Spamcheck, a new data-driven anti-spam engine designed to improve resilience to spam and abuse. Spamcheck has been enabled for all projects on GitLab.com and will be included in the 14.6 release for self-managed customers. The engine was developed by the Security Automation team in partnership with Trust and Safety, Create, and Plan Engineering teams. It leverages a testbed for analysis and prototyping, and is built with a loosely coupled architecture. Deployment is iterative.

1 post · 2019–2021

Timeline

20192026

Feature trailQuiet since 2021

Graviton2 Performance and Cost Optimization

GitLab is evolving its infrastructure strategy to leverage Arm-based Graviton2 processors for both the GitLab application and GitLab Runners. This initiative aims to provide significant cost savings and performance improvements for self-managed GitLab deployments, particularly for customers with high CI/CD compute usage. The focus is on benchmarking and validating the performance and cost-effectiveness of Graviton2 instances compared to traditional x86 instances, enabling customers to optimize their infrastructure. This post details the delivery of official support for 32-bit and 64-bit Arm-based GitLab runners in binary, rpm/deb packaging, and Docker image format, making them available in the 12.6, 12.9, and 13.0 releases respectively.

1 post · 2020–2021

Timeline

20202026

Feature trailQuiet since 2021

Client-side Code Protection

GitLab is enhancing its DevSecOps platform with client-side code protection capabilities, integrating with third-party tools like Jscrambler to provide runtime protection, obfuscation, and anti-tampering measures for JavaScript-based applications. This aims to secure proprietary code, prevent bypasses of app restrictions, and mitigate data exfiltration attacks.

1 post · 2021

Timeline

20212026

Feature trailQuiet since 2021

Application Server Migration (Unicorn to Puma)

GitLab has successfully migrated its application servers from the single-threaded Unicorn to the multi-threaded Puma web server. This migration aimed to address memory growth issues and improve scalability by reducing the number of processes and memory overhead. Puma's multi-threaded model allows for better utilization of CPU and memory, leading to significant memory reduction. The implementation involved extensive testing, tuning of worker/thread configurations, and addressing thread-safety issues. The post also details the use of `unicorn-worker-killer` to manage memory leaks in long-running Unicorn workers by periodically restarting them when memory thresholds are exceeded, ensuring stability and preventing outages.

2 posts · 2015–2021

Timeline

…20172026

Feature trailQuiet since 2021

GitLab Runner's AWS Fargate executor is enhanced to support container building by integrating with AWS CodeBuild. This addresses the limitation of Fargate not supporting privileged containers (required for Docker-in-Docker) by offloading the container build process to CodeBuild. The solution involves configuring GitLab Runner on Fargate to trigger CodeBuild jobs, which then build the container image using a provided buildspec.yml and Dockerfile. This enables building container images within CI/C

1 post · 2020

Timeline

20202026

Feature trailQuiet since 2020

Meltano Data Platform

Timeline

…20172026

Feature trailQuiet since 2016

PostgreSQL Trigram Indexes for Search

GitLab has improved its search performance for PostgreSQL users by implementing trigram indexes. This enhancement allows for faster queries using LIKE conditions, significantly speeding up searches for issues, comments, commits, code, merge requests, and snippets. The implementation involved adapting Rails to support PostgreSQL-specific index types and ensuring compatibility with MySQL.

2 posts · 2016

Timeline

…20172026

Feature trailQuiet since 2015

Customizable Login and Appearance

GitLab Enterprise Edition allows for customization of the login page, including the company logo, title, and description, to provide a branded experience for users. This feature is accessible through the admin area's Appearance settings. Additionally, user preferences have been introduced to customize the UI layout (fluid or fixed width) and the default dashboard view (Projects, Starred Projects, Projects' Activity, or Starred Projects' Activity). Users can also choose between viewing the project's Readme or Activity by default.

2 posts · 2015

Timeline

…20172026

Feature trailQuiet since 2015

On-Premises Chat Integration

GitLab is integrating an open-source, on-premises chat application, Mattermost, into its Omnibus packages. This provides an alternative to Slack for organizations requiring on-premises solutions. The integration includes automatic OAuth configuration with GitLab and aims to simplify setup and management. Future plans include enhanced posting from GitLab and CI to Mattermost.

1 post · 2015

Timeline

…20172026

Feature trailQuiet since 2015

Remote Work Culture and Operations

GitLab has established and refined its fully remote work culture, emphasizing asynchronous communication, flexible work hours, and robust social connection mechanisms. This includes daily morning meetings for coordination and team bonding, a preference for GitLab issues and Slack for communication, and regular individual check-ins with leadership to ensure employee happiness. The company also fosters in-person meetups and virtual social events, particularly around releases, to maintain team cohesion. This post details their lightweight, self-organizing workflow for incoming issues, working and prioritizing, and managing overflow, all while adhering to Agile principles and fostering openness, independence, and responsibility.

1 post · 2015

Timeline

…20172026

Feature trailQuiet since 2015

Version Check Functionality

GitLab has introduced a version check functionality to identify and alert users of outdated installations. This feature aims to improve security, user experience, and reduce the creation of duplicate issues by making users aware of available updates. The system works by loading a small image from a version check server, which indicates the update status (up-to-date, out-of-date, or critical security update). The request includes the GitLab version and server hostname (via HTTP referer) to gather information about usage, with an opt-out option available.

1 post · 2015

Timeline

…20172026

Feature trailQuiet since 2015

On-Premises Deployment Considerations

This feature thread tracks the evolution of GitLab's deployment options, specifically addressing the considerations and benefits of on-premises deployments in contrast to SaaS offerings. It covers aspects like security, integration capabilities, control, performance, flexibility, and data retrieval, highlighting why on-premises remains a viable and often preferred choice for certain organizations.

1 post · 2015

Timeline

…20172026

Feature trailQuiet since 2014

Bug Triage and Reporting

1 post · 2014

Timeline

…20172026