Skip to end of banner
Go to start of banner

Migrating Webhook to Jenkins for Bitbucket

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Current »

This page describes the migration paths of Webhook to Jenkins and all its settings for various cases.

From Server to Data Center

Standard Atlassian Server → DC migration includes app data and configuration settings.

When migrating Bitbucket from Server to Data Center in one of Atlassian’s documented ways (update the license or migrate the database), the app data and settings are maintained with no further action required. All you need to do is update the license for both the platform and any apps.

Bitbucket Server to Data Center (in-place)

Migration is a straightforward task when upgrading your Bitbucket from the Server to the Data Center version on the same instance. Webhook to Jenkins is ready to use in a Data Center environment, and you only need to buy and apply the Data Center license for Webhook to Jenkins.

Updating the app license

To buy the Data Center app license, open the Webhook to Jenkins page at Atlassian Marketplace, click Buy it now, or use this direct link.

To update your license key:

  1. Go to Bitbucket and click Administration ⚙ → Manage appsWebhook to Jenkins for Bitbucket

  2. Click Edit 📝, located to the right of the License key field

  3. Enter your key, click Update, and you are done!

See Atlassian documentation for more details on switching from the Server to the Data Center Bitbucket version.

Bitbucket Server to a new Data Center instance

Full database migration

This case does not differ significantly from the process described in Bitbucket Server to Data Center (in-place). Once you migrate from one instance to another, all hook settings are also migrated. You only need to update the Webhook to Jenkins license when migrating to a different instance type. See Updating the app license for details.

Migrating selected projects

To migrate specific projects or repositories, we recommend cleaning up Bitbucket first by removing any unwanted projects or repos and using the standard Bitbucket front-end (or the Bitbucket REST API for teams that are comfortable scripting). Once your Bitbucket server has only the projects and repositories you want, use a standard Bitbucket migration process to migrate the Bitbucket data. This is the safest and most straightforward migration approach when combining migration and cleanup tasks.

From Server / Data Center to Cloud

A process for migrating your Webhook to Jenkins data is currently under development. Contact Customer Support for more information.

  • No labels