Opscraft
Jenkins · Lesson 10 of 11 · 3 min read

Jenkins vs other CI/CD tools and migrations

Jenkins GitHub Actions GitLab CI Argo CD / Flux
Hosting Self-hosted SaaS (self-hosted runners optional) SaaS or self-hosted In-cluster
Config Jenkinsfile (Groovy) YAML workflows YAML Git manifests (CD only)
Extensibility ~2,000 plugins, Groovy Marketplace actions Built-in features Kubernetes-native
Ops burden High (controller, plugins, upgrades, security) Low Medium Low–medium
Strengths Flexibility, complex enterprise pipelines, on-prem Tight GitHub integration, OIDC to AWS, ecosystem All-in-one DevSecOps Pull-based GitOps deployment

A good senior answer isn't "Jenkins is bad": Jenkins is powerful and flexible but costs operational effort; managed CI reduces toil; GitOps tools handle CD better than push-based pipelines. Many orgs run CI in Jenkins or Actions and CD with Flux/Argo.

Migrating Jenkins → GitHub Actions

  1. Inventory jobs: what each does, triggers, credentials, agents, plugins used, owners. Delete dead jobs.
  2. Map concepts: agents → runners (GitHub-hosted or self-hosted on EKS via Actions Runner Controller), credentials → GitHub secrets/environments + OIDC to AWS, shared libraries → reusable workflows and composite actions, approvals → environment protection rules.
  3. Build reusable workflow templates for the common pipeline types.
  4. Migrate in waves, starting with simple repos; run both systems in parallel briefly and compare results.
  5. Decommission Jenkins jobs and finally the controller; archive build history if compliance needs it.
Enlarge diagramInventoryjobs, credentials,plugins; deletedead jobsMapagents → runners,credentials →OIDCTemplatesreusableworkflowsWavessimple reposfirst, run bothbrieflyRetirearchive history,shut down12345
Figure 1. Migrating from Jenkins to GitHub Actions in waves.
Swipe sideways to see all of it, or tap to open it full screen.

Migrating freestyle jobs to pipelines

Standardise on shared-library templates, generate the pipelines with Job DSL or Organization Folders, migrate team by team, and lock down freestyle job creation.