Some remote repository hosting systems support migrating their repositories (including their pull requests) from one server instance to another. To continue using remote repository integrations after repository migration, you may either create a new integration pointing to the new repository URL, or migrate the existing integration to the new URL as described in this topic. When creating new remote repository integration, links from the existing reviews would remain unchanged and would lead to the previous location of the repository. When migrating existing integration,  links from the existing reviews would be updated and will lead to the new location of the repository.

Migration procedure

To migrate an existing repository hosting integration, you need to call the AdminRemoteSystemService.migrateRemoteSystem command and then update the integration webhook using the AdminRemoteSystemService.updateWebhook command.

Call the following JSON API commands:

[

{"command" : "SessionService.getLoginTicket",

        "args":{"login":"serveradmin","password":"somepassword"}},

{"command" : "AdminRemoteSystemService.migrateRemoteSystem",

        "args":{

               "fromRepo": "https://bitbucket.org/TeamName/OldRepoName",

                 "toRepo": "https://bitbucket.org/TeamName/NewRepoName"}},

{"command" : "AdminRemoteSystemService.updateWebhook",

        "args":{"id":"<id>"}}

]

To learn the ID of the desired integration, you can list all available remote system integrations using the AdminRemoteSystemService.getIntegrations command:

[

{"command" : "SessionService.getLoginTicket",

        "args":{"login":"serveradmin","password":"somepassword"}},

{"command" : "AdminRemoteSystemService.getIntegrations","args":{}}

]

How it works

The AdminRemoteSystemService.migrateRemoteSystem command performs the following actions:

Technical details and limitations