Not long ago, I had to migrate Jenkins jobs from an old server to a new one. That’s where StackOverflow comes into the play, below the most voted answers I found:
- Jenkins CLI
- Copy the jobs directory
- Jenkins Remote API
- Jenkins Job Import Plugin
In spite of their advantages, those solutions comes with their downsides especially if you have a large number of jobs to move or no access root to the server. But, guess what ? I didn’t stop there. I have came up with a CLI to make your life easier and export/import not only Jenkins jobs but also plugins like a boss.
To get started, find the appropriate package for your system and download it. For linux:
Note: For Windows make sure that butler binary is available on the PATH. This page contains instructions for setting the PATH on Windows.
Once done, verify the installation worked, by opening a new terminal session and checking if butler is available :
1 – Plugins Management
To export Jenkins jobs, you need to provide the URL of the source Jenkins instance:
butler plugins export --server localhost:8080 --username admin --password admin
As shown above, butler will dump a list of plugins installed to stdout and a new file plugins.txt will be generated, with list of installed Jenkins plugins with name and version pairs:
Now, to import the plugins to the new Jenkins instance, use the command below with the URL of the Jenkins target instance as an argument:
butler plugins import --server localhost:8080 --username admin --password admin
Butler will install each plugin on the target Jenkins instance by issuing API calls.
2 – Jobs Management
To export Jenkins jobs, just provide the URL of the source Jenkins server:
butler jobs export --server localhost:8080 --username admin --password admin
A new directory jobs/ will be created with every job in Jenkins. Each job will have its own configuration file config.xml.
Now, to import the jobs to the new Jenkins instance, issue the following command:
butler jobs import --server localhost:8080 --username admin --password admin
Butler will use the configuration files created earlier to issue API calls to target Jenkins instance to create jobs.
Once you are done, check Jenkins and you should see your jobs successfully created :
Hope it helps ! The CLI is still in its early stages, so you are welcome to contribute to the project in GitHub.
Drop your comments, feedback, or suggestions below — or connect with me directly on Twitter @mlabouardy.