FAQ: GitLab CI/CD Catalog

What this post added

This post is an FAQ that clarifies and expands upon the capabilities of the GitLab CI/CD Catalog. It addresses questions regarding component versioning (supporting branches and tags), the creation of composite components, various testing strategies (commit-based, child pipelines), referencing branches as versions, populating self-managed catalogs, mirroring components, preventing job name collisions using inputs, inspecting component source code, supporting array inputs, limitations compared to CI Steps, best practices, roadmap items for private components and group-specific component usage, the relationship between CI Steps and components, managing forks, creator verification processes, recommendations for integrating external tools like Fortify SCA, the roadmap for component outputs (CI Steps), plans for component labeling and discoverability, the migration of existing CI/CD templates to components, and recommended approaches for transitioning from existing templates to catalog components.