Category Direction - Component Catalog

1. You are here:
2. GitLab Direction
3. Verify Stage Direction
4. Category Direction - Component Catalog

• Component Catalog
  • Introduction and how you can help
• Overview
  • Strategy and Themes
  • Roadmap
    • What are we currently working on
    • Analyst Discussion
    • What we recently completed
  • Best in Class Landscape
    • Key Capabilities
• Dogfooding
• Competitive Landscape
• Glossary

Component Catalog

Stage	verify
Maturity	Minimal
Content Last Reviewed	2025-05-14

Introduction and how you can help

Thanks for visiting this direction page on the Components catalog category at GitLab. This page belongs to the Pipeline Authoring Group in the Verify Stage and is maintained by Dov Hershkovitch. You can submit your feature requests using GitLab issue tracker.

Overview

We aim to foster a collaborative community of developers who can easily share, build, and maintain high-quality CI/CD configurations. By providing a platform that serves as a centralized hub for managing all DevOps-related assets within an organization, we aim to empower developers to focus on true innovation and unlock the full potential of the open-source ecosystem. Through our commitment to inclusivity, transparency, and accessibility, we strive to create a continuous learning and improvement culture where every community member can contribute.

Strategy and Themes

DevOps is all about speed, it delivers value faster by shortening the software development life cycle. Organizations that want to accelerate their DevOps adoption need to set up a working pipeline so other teams can use it to automate their workflow. During the development of a pipeline configuration, engineers frequently encounter the following challenges:

1. "Where can I find it?" - Whenever engineers embark on setting up a new pipeline, they often search for existing pipelines in their organization or externally. This is because someone, at some point, has likely attempted to configure a similar pipeline.
2. "How do I use it?" - After engineers locate a suitable pipeline to work with, they require clear instructions on effectively using it. This guidance is crucial for understanding the pipeline's functionalities and ensuring its proper usage.
3. "Does it always work as expected?" - Engineers often question whether the pipeline is consistently reliable and delivers the expected results. They also evaluate its reusability and whether it can be shared effectively with other teams within the organization. These aspects are vital for determining the pipeline's suitability for wider adoption and collaboration.

While it is possible to solve each problem separately, GitLab believes that we need to solve those problems holistically by building a framework that contains tools that add functionality and improve your CI/CD workflow. We aspire to provide the best-in-class experience for building and maintaining CI/CD pipelines.

Our strategy is to provide an opinionated framework that:

1. Is the SSoT for users to browse and search for the desired pipeline components.
2. Contains shareable and reusable package components that could be attached to any CI/CD configuration.
3. Has an easy way to document the usage of each component.
4. Fosters a collaborative methodology by allowing users to contribute to the catalog by developing and publishing their own components.

We should adopt a bottom-up approach to construct this solution, starting with the smallest building blocks and gradually progressing upwards. By starting from the foundational elements and gradually building on them, we can create a robust and cohesive solution.

Roadmap

We aim to enhance our CI/CD catalog by introducing features tailored for enterprise customers, thereby delivering additional value to their operations.

• Support .com components in Self Manage instance - In our effort to support all customer segments we would like to help our Self manage customers and customers in an air-gapped environment to easily consume components that exist today in our .com catalog. This approach aligns with our goal, where every customer, regardless of their setup, can readily explore and implement additional functionalities from our platform.

• Developer security workflows - When publishing or utilizing CI components, teams require a secure and reliable method to verify that the components are free from vulnerabilities and tampering. This safeguards CI/CD pipelines from potential security risks while preserving trust in both internal and third-party components.

• Component analytics dashboard - We aim to provide visibility into component usage across project pipelines across organizations by addressing the current lack of traceability. This enhancement will empower users with seamless control over component management, enabling them to quickly identify which projects are using outdated versions, notify relevant teams, ensure required components are included, and support full lifecycle management—including deprecation. By providing clear insights into component usage, we promote precise version control and better project alignment, allowing users to take timely corrective actions and maintain consistency across pipelines.

• Restrict who can publish components to the Catalog - We aim to provide GitLab admins with the ability to restrict specific individuals or groups from publishing components to a catalog. This feature would enable organizations to enforce tighter control over catalog contributions, ensuring only authorized users or teams can publish components.

• Block users from using unofficial components - We want to allow administrators to restrict component domain usage to specific users or groups, ensuring tighter governance and alignment with organizational policies. This capability reflects our commitment to delivering a refined catalog experience that meets enterprise needs while fostering a secure and well-regulated ecosystem

• Mature the CI/CD catalog to a competitive maturity level - We aim to advance the CI/CD catalog to a competitive level of maturity by introducing capabilities that enhance both functionality and user experience. This includes adding advanced search and filtering options, improving page navigation, and delivering targeted UI enhancements. These improvements will provide robust features, seamless usability, and enterprise-grade governance, ensuring the catalog effectively supports the diverse needs of users, aligns with organizational goals, and strengthens GitLab’s position as a leader in CI/CD pipeline management.

• Intelligent search powered by generative AI - Unlike traditional keyword-based searches, Intelligent Search understands the intent behind user queries, enabling it to provide more accurate and relevant results. In addition, we can leverage AI to prompt for more information about specific inputs required by the user, which will result in configured and fine-tuned components with the relevant inputs. This could enhance the user experience and streamline the process of selecting, configuring, and using components from the catalog.

What are we currently working on

Inputs enhancments - Inputs are the recommended way to pass any parameter to a component. It has multiple benefits over the usage of variables, and since its launch, it has been widely adopted by our users and customers. This is why we decided to continue our investment in inputs and increase its scope and flexibility.

• Enhancing the Release Process of the catalog - A crucial step in reaching our goal is refining the release process for adaptability. This adjustment will enable us to efficiently and effectively release any resources to the catalog.

Analyst Discussion

• Notes from Gartner discussion (internal)
• Related articles
  • DevEx, a New Metrics Framework from the Authors of SPACE
  • DevEx: What Actually Drives Productivity

What we recently completed

Support inputs for pipelines - Today, when creating a pipeline, we rely on CI variables to inject dynamic content into the pipeline. Inputs provide a superior interface for this purpose since only the specified inputs can be passed. Inputs support basic types of validation. The input lifecycle is scoped to the pipeline creation via text interpolation.

Best in Class Landscape

BIC (Best In Class) is an indicator of forecasted near-term market performance based on a combination of factors, including analyst views, market news, and feedback from the sales and product teams. It is critical that we understand where GitLab appears in the BIC landscape.

Key Capabilities

1. Centralized Component Catalog: Create a centralized component catalog that serves as a single source of truth for users to browse and search for pipeline components. The catalog should be easily accessible and provide comprehensive information about each component, including its purpose, usage, and documentation.
2. Shareable and Reusable Components: Enable users to develop and publish their pipeline components to the catalog. Components should be designed to be shareable and reusable, allowing developers to easily attach them to their CI/CD configurations. This promotes collaboration and reduces duplication of effort within the organization.
3. Versioning: Implement versioning for components to ensure users can pin their pipelines to a specific component revision. This helps in maintaining stability and allows for controlled updates.
4. Component Abstraction and Encapsulation: Encourage the development of components that abstract away complex pipeline configuration units. Components should encapsulate implementation details and provide a clear interface, enabling users to use them without needing to know the underlying details.
5. Documentation: Provide a mechanism for users to document the usage of each component. This should include clear guidelines, examples, and best practices to help users understand how to use the components effectively.
6. Collaborative Contribution: Foster a collaborative community where developers can contribute to the component catalog by developing and publishing their own components. Implement mechanisms for peer review, feedback, and contribution management to ensure the quality and reliability of the catalog assets.
7. Accessibility: Design the platform to be inclusive and accessible to all community members. Provide intuitive interfaces, clear navigation, and comprehensive search capabilities, making it easy for users to find the components they need.
8. Continuous Improvement and Learning: Establish a culture of continuous learning and improvement within the community. Encourage feedback from users, collect analytics on component usage, and iterate on the catalog based on user needs and preferences. Regularly update and enhance the catalog with new components, improved documentation, and additional features based on community contributions.
9. Securing users workflow: - we are committed to providing our users with means to ensure the security and reliability of their workflows and underlying capabilities

Dogfooding

The best way to understand how GitLab works is to use it for as much of your job as possible, this is why we practice dogfooding. We have recently begun collaborating with these internal teams in GitLab which expressed their desire to dogfood some of our features:

• Engineering Productivity team - This effort is tracked through this collaboration issue, and the team is currently identifying commonly used CI/CD templates and attempting to convert them into components. Our goal is to understand our customers' challenges when converting their templates into components.
• Incubation team - This effort is tracked through this collaboration issue.
• Secure team - We've converted some of our existing templates such as SAST, Secret detection, and more. This effort is tracked through this collaboration issue.

Competitive Landscape

Notable competitors in this space are:

• GitHub actions with their actions marketplace.
• Circle CI orbs.
• CodeFresh also provide their users with a CI step library.

Watch this walkthrough video of the different contribution frameworks available by these competitors:

Glossary

This section defines the terminology used throughout this project. With these terms we are only identifying abstract concepts, and they are subject to changes as we refine the design by discovering new insights:

• Component: A reusable single pipeline configuration unit. Use them to compose an entire pipeline configuration or a small part of a larger pipeline..
• Component Project: A component project is a GitLab project with a repository that hosts one or more components..
• Catalog: Collaborative platform that presents the collection of CI/CD projects and components.
• Version: The release name of a tag in the project, which allows components to be pinned to a specific revision, components of the same project and versioned together.