The Jenkins for Jira app support migrations via the Jira Cloud Migration Assistant, or JCMA for short. Migrations scheduled and performed using this method are listed as an Import migration under Export/Import.
From there you can keep track of the progress of the migration as well as review and next steps or errors.
How a migration is imported
The Jira Cloud Migration Assistant hands the data of your Jira Data Center app over in parts, in no particular order. The app collects all parts first, and only imports them once everything the server exported has arrived. The data is then imported once, in the order it depends on each other: the app configuration, then the Jenkins sites, their jobs, the builds of those jobs, and finally the links between builds and issues.
The following is migrated:
- the app configuration,
- the Jenkins sites, including their jobs and builds,
- the links between builds and Jira issues.
Data that is already in your cloud site
A migration is added to the data your Jira Cloud site already has, it never replaces it. Nothing is removed from your cloud site before or during a migration, so Jenkins sites you connected in the cloud before you migrated are still there afterward.
Every Jenkins site, job, and build keeps the identity it had on the server it was migrated from, which means that:
- Migrating the same server again only updates its own data. You can run a test migration first, migrate in phases, or run a migration again after it did not complete. Sites, jobs, and builds that were migrated before are updated, new ones are added, and nothing is duplicated.
- Several servers can be migrated into one cloud site. When you consolidate more than one Jira Data Center instance, each migration only touches the Jenkins sites, jobs, and builds of its own server.
- Data removed on the server is not removed from the cloud. A Jenkins site or job you deleted on the server between two migrations stays in your cloud site until you delete it there.
The result of a migration
A migration ends in one of the following states, which is also what the Jira Cloud Migration Assistant is told.
| State | What it means | What to do |
|---|---|---|
| Success | Everything the server exported was imported. | Follow the next steps listed with the migration, like registering your Jenkins sites. |
| Incomplete | Part of the data was imported and part of it was not. The errors of the migration list what was not imported, such as the builds of a job that could not be imported. | Review the errors and run the migration again. What was imported already is updated, not duplicated. |
| Failed | Nothing could be imported, or the server reported an error while it exported. | Review the errors and run the migration again. |
| Timed out | Not all the data of the server arrived, or the import took longer than it may. A migration waits several hours for its data before it gives up. | Check that the export on the server completed and run the migration again. |
| Cancelled | The migration was cancelled from the Jira Cloud Migration Assistant. Data that was imported before the cancellation is kept. | Run the migration again when you are ready. |
A migration only ends as a success when all of its data was imported. When a job cannot be imported, the builds that belong to it are not imported either, and the migration tells you so instead of leaving them out silently.
Previous: Link Index
Next: Errors
