Skip to content

CI/CD · Jenkins · GitLab CI · GitHub Actions

Migrating from Jenkins: a practical checklist

How to move legacy Jenkins jobs to GitLab CI or GitHub Actions safely — inventory, templates, parallel runs and cut-over.

· 5 min read

First, decide whether to migrate at all

Jenkins is still a capable tool. If your jobs are already defined as Jenkinsfiles, plugins are maintained and someone owns the server, modernising Jenkins may be cheaper than migrating. Migration makes most sense when your code already lives in GitLab or GitHub and the Jenkins server has become a maintenance burden.

1. Build an inventory

  • List every job with its owner, trigger, last successful run and downstream dependencies
  • Note credentials, plugins and agents each job relies on
  • Mark each job as migrate, merge or retire

2. Design shared templates

Most jobs follow the same pattern: install dependencies, test, build an artefact or image, deploy. Create reusable templates (GitLab CI includes or GitHub reusable workflows) so each repository needs only a short pipeline file.

3. Move secrets out of job configuration

Store credentials as protected CI variables or in a secrets manager such as AWS SSM, Azure Key Vault or HashiCorp Vault. Rotate any credential that has lived in Jenkins configuration for a long time.

4. Run old and new pipelines in parallel

Start with a low-risk repository. Let both pipelines run until their outputs match, then switch deployments to the new pipeline. Repeat repository by repository.

5. Decommission carefully

  • Disable jobs before deleting them and keep a backup of the Jenkins home directory
  • Remove credentials Jenkins no longer needs
  • Shut the server down only after a full release cycle without it

← All guides

Want a second opinion on your setup?

Our Cloud & Infrastructure Audit gives you a prioritised, written action plan.