Static Code Analysis with Gitlab CI
summary
Shows a GitLab CI pipeline that runs static analysis by compiling the whole project, running clang-tidy and clazy only on files changed in the merge request, and publishing a code quality report inside the MR view. Handles generated Qt files by doing a full build (slow, hits a one-hour runner timeout), so the practical optimization is checking only changed files to fit time limits. Implementation exists as an include file in a sysadmin repo, works but is pending polishing and merge.
AI-written summary · about
chapters (12)
- 0:00Intro
- 0:48Static Analysis 101
- 1:36Clazy - Qt Containers & Range-based for loop
- 6:13GitLab CI
- 7:11How do I get it?
- 11:21What exactly does it do?
- 15:14What does it look like?
- 16:14Customization - analyzers
- 17:22Customization - Clazy
- 18:09Customization - Clang-tidy
- 19:44Conclusion
- 20:51Thank you!
related talks
05mSet it and forget it!
17mShift-Left Security in Practice with Gitlab
47mComputer Says No — Static analysis and CI in a Kotlin world
11mRealizing DevSecOps with GitLab and Infrastructure as Code
40mSecure by Default: Building an AI-Augmented, OSS-Powered Reusable CI/CD Pipeline
46mDevelop your CI tools
11mGitLab CI Integration: Automated Testing and Deployment
30mAutomating Code Quality