Quality Beyond Testing: Jenkins to GitHub Actions Migration: Optimized Processes & QA
summary
Case study reports a migration from Jenkins to GitHub Actions that runs in about three months, replacing three Jenkins instances and ~45 plugins with migrated Jenkins to GitHub Actions workflows, GitHub-hosted and self-hosted runners, and built-in secrets. Pipelines shrink from ~800–850 Groovy lines to ~175 YAML lines, integrate JFrog Artifactory, Slack, Red Hat Ansible, and Jira, increase deployment throughput and stability, and deliver a 35% increase in developer efficiency.
AI-written summary · about
chapters (15)
- 0:00DevOps and CI/CD pipelines
- 2:12Jenkins pain points and migration
- 5:49Why GitHub Actions chosen
- 7:54GitHub Actions fundamentals
- 11:27Jobs steps and workflows
- 13:14Third-party actions security
- 16:30Community actions risks
- 19:46Runners and self-hosted
- 21:33Migration process challenges
- 25:02Case study .NET DLP pipeline
- 28:50Efficiency gains after migration
- 29:56Case study nCscope test execution
- 32:50Operational reliability gains
- 35:00Cultural shift in pipelines
- 37:14Q&A
related talks
43mRewriting an Old CI/CD on GitHub Actions for 280 Contributors?
55mGitHub Actions - CI:CD and more
47mLights, Camera, GitHub Actions!
19mHow we migrated the CI / CD of our Android app to GitHub Actions
30mPragmatic, scalable, and ergonomic CI/CD using Github Actions and K8s.
25mFrom Hero to Zero Effort–Simplifying CD
45mLights, Camera, GitHub Actions!
48mCICD with Github Actions