← Back to Roadmap
Remove Jenkins / Migrate to GitHub Actions
Not Started Overall Progress 0%
0 of 6 tasks completed
Tasks
- ☐ Audit all Jenkins jobs and pipelines
- ☐ Design GitHub Actions workflow templates
- ☐ Migrate build pipelines to GitHub Actions
- ☐ Migrate deployment pipelines
- ☐ Migrate scheduled/cron jobs
- ☐ Decommission Jenkins servers
Overview
Migrate all CI/CD pipelines from self-hosted Jenkins to GitHub Actions, eliminating the operational burden of maintaining Jenkins infrastructure and modernizing the deployment workflow.
Business Value
- Cost Savings: Eliminate Jenkins EC2 instances and maintenance overhead
- Developer Experience: Native GitHub integration, PR-triggered workflows
- Security: Eliminate a self-hosted attack surface
- Reliability: GitHub-managed infrastructure with built-in redundancy
Technical Approach
Audit all existing Jenkins jobs (builds, deployments, cron tasks). Design reusable GitHub Actions workflow templates. Migrate in phases: builds first, then deployments, then scheduled jobs. Run parallel pipelines during transition.
Risks
- Some Jenkins plugins may not have GitHub Actions equivalents
- Build minutes pricing needs to be monitored
- Self-hosted runners may be needed for VPC-internal deployments