Learn how reusable CI/CD components and the catalog help with efficiency on a DevSecOps platform. We will walk through the adoption path of CI/CD components and the catalog and show how a component is structured with a practical Rust example. Inputs for reusability also provide dynamic job names.

Testing, documenting, and releasing a CI/CD component concludes the learning. At the end of the talk, an extra section for a hands-on migration workshop of a Golang CI/CD template into a CI/CD component awaits. Start your DevSecOps efficiency journey today.

Speaker: Michael Friedrich, Senior Developer Evangelist, @dnsmichi
Public slides: https://go.gitlab.com/VYS051
CI/CD components docs: https://go.gitlab.com/gZnB2V
CI/CD components, catalog, inputs feedback issue: https://go.gitlab.com/J3xcU5
GitLab Forum & Discord: https://go.gitlab.com/tokv3L

Recording date: 2024-01-22

Note: This talk will be maintained by the Developer Relations team throughout FY25, organization epic: https://gitlab.com/groups/gitlab-com/... and future recordings will replace this content item.

Table of Content

0:00 Introduction
0:59 Efficient DevSecOps?
2:44 CI/CD Efficiency
4:33 User journey
5:22 Inside a component
7:17 Practical Example: Rust
9:33 Consume the Rust CI/CD component
12:02 Optimize: Dynamic inputs
15:05 Dynamic job names
17:58 More optimization
19:29 How to test a component
20:43 Test programming language component with source code
21:50 Documentation
22:39 Add to CI/CD catalog
23:05 Release a component
24:24 Visibility in the CI/CD catalog
25:42 User value: Building blocks
27:59 More use cases
29:45 Component types
31:00 Everyone can contribute
31:30 Migration workshop: Golang CI/CD template to component (optional, first iteration)
33:10 Migration: Analyze existing template
34:23 Migration: Define optimization strategy
36:55 Migration: Template directory structure
38:03 Migration: Create build template in the component
39:57: Migration: format, test templates
40:40 Migration: Test the CI/CD component
41:45 Migration: Add Go source code (using GitLab Duo Code Suggestions)
43:24 Migration: Verify results, add documentation
44:37 Slides URL/QR Code
44:40 Conclusion