Git Integration for Jira Self-Managed (Data Center/Server) Documentation

Contact Support
GitKraken Status  

Upgrades and migrations within same server

The following instructions are for in-place upgrades + migrations of Jira on the same server (typically when upgrading version of Jira). See Migration to another server instructions for migrations to another server.

We strongly recommend performing your migration in a test environment first. Do not migrate your production Jira server application until you are satisfied that your test environment upgrade is successful.

 

GitServer ➜ GitServer

Do note that the steps outlined in this section are also applicable to Jira Data Center instances.

Migration within the same server when Jira HOME path is unchanged

Before you upgrade/migrate

  1. We recommend Jira admins to upgrade to the latest version of Git Integration app from the Atlassian Marketplace.

  2. Run the instance for some time (a few days) and once the testing is stable – then do the migration.

Upgrade/migrate

Please follow the standard instructions from Atlassian for upgrading on the same server (select your Jira version).

No extra steps are required.

After you migrate

Verify that configured integrations and repositories in the Manage Git repositories screen are correct and indexed properly.

 

Migration within the same server when Jira HOME path is changed (Classic)

Pros:
Easy for migration.

Cons:

  • You will have to set up all your repository settings again (including mapping to projects and repository watchers.
  • Users are required to re-setup their PATs after upgrade/migration.
  • Afterwards, do a full reindexing for all your repositories.

Before you migrate

  1. We recommend Jira admins to upgrade to the latest version of Git Integration app from the Atlassian Marketplace.

  2. Run it for some time (a few days) and once the testing is stable – then do the migration.

  3. Use the Git Integration Bulk Change export to backup the integration settings and extract/save credentials for repositories.

Please note that bulk export data contains lines for all repositories — including those that were automatically created within integrations. You need only the data for ‘top-level’ repositories and integration to reconnect to all your repositories.

Upgrade/migrate

Please follow the standard instructions from Atlassian for upgrading on the same server (select your Jira version).

No extra steps are required.

After you migrate

  1. With Git Integration for Jira app, remove all repositories in Manage Git repositories.

  2. Remove all repositories data from the /data/git-plugin/ folder in the new Jira home directory (i.e. remove all folders which have the next format: '<repositoryID>_<repositoryName>')

  3. Reconnect to all integrations/repositories using new or existing credentials. Your stored SSH keys will stil be migrated automatically.

 

Migration within the same server when Jira HOME path is changed (Recommended)

Pros:

  • Repository settings and user’s PATs are preserved.
  • Reconnection of all integrations is not required.
  • No extra steps after bulk import post-migration

Cons:

  • You will have to change internal configuration files for the GitServer plugin. This should be done with extreme care.

Before you migrate

  1. We recommend Jira admins to upgrade to the latest version of Git Integration app from the Atlassian Marketplace.

  2. Run it for some time (a few days) and once the testing is stable – then do the migration.

  3. Use the Git Integration Bulk Change export to backup the integration settings.

  4. Open the backup file with your favorite text editor and replace all occurrences of the old Jira home path with the new Jira home path.

Upgrade/migrate

Please follow the standard instructions from Atlassian for upgrading on the same server (select your Jira version).

No extra steps are required.

After you migrate

Use Git Integration for Jira app: Bulk import to load the updated backup file with the new Jira home path. This should reconnect all existing integration repositories as it was before the backup.

 

GitServer ➜ GitDataCenter

If you are thinking of migrating your server installtion to Data Center, read the guidelines below to help you get up and running.

Before you migrate

  1. We recommend Jira admins to upgrade to the latest version of Git Integration app from the Atlassian Marketplace.

  2. Run it for some time (a few days) and once the testing is stable – then do the migration.

Migration

After you migrate

Atlassian recommends using the applicable database backup tools in general BUT for migrations – Atlassian recommends using the Jira XML backup (helps when migrating to new OS / database / version of Jira)

 

More related Administration articles

General settings

Upgrades and migrations within same servver (this page)

Migration to another server

Scheduling jobs

Recommended Jira memory settings

Plugin Data Storage

Indexing queue explainer

Have feedback about this article? Did we miss something? Let us know!
On this page