Using CI Templates for Speed and Consistency
summary
Company builds an internal CI template library stored in a repo with latest/stable branches, where base pipelines are three-line includes that provision builds, tests, and security scans. Template jobs use variables, project access tokens and instance variables, pull zipped defaults from the package registry, and are configurable per project. SonarQube and other external scanners are replaced by GitLab SAST, dependency scanning and secret detection (container scanning optional). New project setup drops from days to minutes and into 3 clicks.
AI-written summary · about
chapters (13)
- 0:00Introduction to CI templates
- 1:23Project setup challenges
- 3:18Designing the template library
- 4:45Structuring and using templates
- 5:45Writing reusable job templates
- 8:18Developing the template library
- 9:39Assembling the pipeline
- 11:02Adding creative CI features
- 12:38Customizing code quality scans
- 14:22Visual reports and linting
- 15:41Achieving automation goals
- 17:11Security and vulnerability management
- 19:20Results and final thoughts
related talks
01h 10mCreating efficient, convenient and reliable CI
17mShift-Left Security in Practice with Gitlab
40mSecure by Default: Building an AI-Augmented, OSS-Powered Reusable CI/CD Pipeline
15mUsing GitLab to Power our Frontend Technical Interviews
24mCI/CD Best Practices to Deliver Software Faster
11mGitLab CI Integration: Automated Testing and Deployment
36mAvoid Chaos in Our CI/CD Pipelines with Inner Source
29mTrusted Software Supply Chain with JTE