Migrate from Jenkins to GitHub Actions
Freestyle, multibranch and Pipeline jobs, declarative or scripted, and the shared libraries behind them. CodeCargo groups similar jobs into families and converts each family once, onto reusable workflows your platform team owns.
Runs in the app, with our team on call@Library('corp-pipelines') _
cdAnsibleBuild(
appName: 'facturacion',
inventory: 'inventories/pro/hosts',
branch: "${env.BRANCH_NAME}"
)name: deploy
on:
push:
branches: [main]
jobs:
deploy:
uses: acme/corp-pipelines/.github/workflows/cd-ansible-build.yml@v3
with:
app-name: facturacion
inventory: inventories/pro/hosts
secrets: inheritTrusted by teams moving to GitHub at scale
What moves
Everything your Jenkins estate runs on.
Every job type
Freestyle, matrix, multibranch, Pipeline from SCM and inline Pipeline jobs.
Declarative and scripted
Both are converted; scripted control flow is restructured, not copied line by line.
Shared libraries
Each library function becomes a reusable workflow that many repositories call.
Folders and multibranch
Organization folders and multibranch jobs are resolved to the repositories they build.
Credentials
Credential definitions are inventoried and mapped to GitHub secrets. Values are never extracted.
Plugins
Every plugin in use is listed and mapped to an action, a building block or a secret.
- Jenkins plugins recognized and mapped during import
- 567
- freestyle, matrix, multibranch, Pipeline from SCM and inline Pipeline
- 5 job types
- per shared-library function, not one per Jenkinsfile
- 1 workflow
How it maps
Jenkins concepts, in GitHub Actions terms.
Plugins without a match map to your own building blocks, so every team lands on the same steps.
| Jenkins | GitHub Actions |
|---|---|
| agent { docker { image 'node:20' } } | container: node:20 |
| tools { maven 'M3' } | actions/setup-java + actions/cache |
| archiveArtifacts | actions/upload-artifact |
| junit | dorny/test-reporter |
| withCredentials | ${{ secrets.NAME }} |
| parameters { string(...) } | workflow_dispatch.inputs |
| triggers { cron('H 2 * * *') } | on: schedule |
| post { failure { ... } } | if: failure() |
| input (approval) | Environment with required reviewers |
| @Library('corp-pipelines') | uses: corp-pipelines/.github/workflows/… |
No surprises at cutover.
The parts that need a person are named in the plan up front, so they are decided before cutover, not discovered during it.
What needs a person
- Which self-hosted runner labels each job should use
- Plugins with no equivalent yet, and deprecated plugins worth retiring
- Credential values, which are re-entered in GitHub, never copied out of Jenkins
Jenkins-specific
- Shared-library functions land first as reusable workflows, then the jobs that call them move in waves
- Multibranch and organization folders are mapped to repositories before conversion starts
- Jobs stay runnable in Jenkins until each team cuts over
The same method for every Jenkins estate.
See the full method- 01Inventory everything
- 02Convert families, not files
- 03Ship in waves of pull requests
- 04Cut over with rollback
Your migration, your way
Run it yourself, or run it with us.
Self-serve
Migration Assistant
The whole program in one app: inventory, families, waves of pull requests and cutover. Built for platform teams who want to drive.
- Inventory, families, waves and cutover in one app
- Pull requests to repository owners, not tickets
- Start free on 10 repositories, no card
With our migration team
Migration services
We scope, plan and run the move alongside your team, on the same platform, for the estates and deadlines that can't slip.
- GitHub Enterprise Cloud to EMU and data-residency moves
- Scoping, wave plans and cutover support
- The custom pipelines nobody wants to touch
- A team that has done this at enterprise scale
After the move
Land clean, then stay clean.
CodeCargo Manage keeps every repository on the standards and building blocks you migrated onto, fixing drift as pull requests, as far on its own as you allow.
Jenkins migration questions.
Don't see yours? Our migration team will walk through your Jenkins estate with you.
Can CodeCargo convert scripted Jenkins pipelines?
Yes. Declarative and scripted pipelines are both converted. Scripted control flow such as try and catch is restructured into GitHub Actions conditions and steps rather than copied line by line.
What happens to our Jenkins shared libraries?
Each shared-library function becomes a reusable workflow. The jobs that called the library then call that workflow, so a change in one place reaches every repository.
Do you copy our Jenkins credentials?
No. Credential definitions are inventoried and mapped to GitHub secrets, but values are never extracted from Jenkins. They are entered in GitHub once.
How do you handle Jenkins plugins?
Every plugin in use is listed during import and mapped to an action, one of your building blocks, or a secret. Plugins with no equivalent are flagged in the plan before anything converts.