Create usable components for the Global Catalog
Goals
-
Create 10
GitLab-maintained CI components to be used in GitLab projects for dogfooding (Q4 OKR) - @fabiopitino-
[WIP] Determine ownership and maintenance of GitLab-maintainer CI Components after they're created
-
-
Leverage community contributions with a competition amongst contributions to grow the catalog with components - see Slack announcement - @dhershkovitch -
[WIP] Convert popular CI Templates to reusable CI Components (e.g. Determine what CI Templates will be converted to CI Components when, and which teams will be converting them) - @marknuzzo
Remaining Priorities (as Ordered)
- Define where GitLab-maintained component reposi... (#411872 - closed) is the top priority as once people start to use these components we cannot move them easily due to the path. (Awaiting scheduling of issue)
- We can start with Backend: Provide components as helpers to test ... (#430818) since they would be useful for all users (Awaiting scheduling of issue)
- Then continue with the popular CI templates or have Engineering Productivity extract reusable components from our CI pipelines.
- Finally continue with converting some popular CI templates.
Potential Strategies
- Create GitLab CI components based on some of the most popular GitHub Actions - e.g. ordered by most installed/starred
-
@fabiopitino
noted that it's important to differentiate what we could better understand how best to tradeoff between using CI Steps to run GH Actions vs trying to recreate these as CI Components
-
- Create components based on our "most popular" CI Templates (Do we have this usage data readily available?)
- Will be completed by either the Pipeline Authoring team or via internal dogfooding with our other Engineering teams (such as Engineering Productivity) - @marknuzzo can you confirm the strategy with the team?
GitLab Components Repository
To be confirmed - https://gitlab.com/gitlab-components
Edited by Cheryl Li