Bitbucket Server upgrade guide
Bitbucket のインストールまたはアップグレード
このページの内容
このセクションの項目
関連コンテンツ
- 関連コンテンツがありません
This guide describes how to upgrade your Bitbucket Server installation to the latest version on Windows or Linux using the installer.
現在有効なソフトウェア メンテナンスがある場合、新しいバージョンへのアップグレードは無料で行えます。詳細については、「ライセンスの FAQ」を参照してください。
Other ways to upgrade Bitbucket:
- Manually – upgrade using an archive file.
- Data Center – Data Center クラスタをアップグレードします。
- ローリング アップグレード - ダウンタイムなしで、Data Center クラスタを次のバグ修正バージョンにアップグレードします。
- Docker container image for Bitbucket Server.
はじめる前に
Before you upgrade Bitbucket there are a few questions you need to answer.
Is using the installer the right upgrade method for you? |
詳細を読む...
You can choose to upgrade using the installer, or, if the installer is not suitable for your situation you can use an archive file to update your Bitbucket Server instance. Only use an archive file to update Bitbucket Server if the installer is not suitable for your situation, as the installer is the the recommended approach to upgrade for most use cases. Read about how to upgrade Bitbucket Server from an archive file.
|
アップグレードの資格がありますか? |
詳細を読む...
To check if software maintenance is current for your license, go to ![]() サポート期間が失効しいる場合、プロンプトに従ってライセンスを更新し、再適用してからアップグレードを行います。
|
Have our support platforms changed? |
詳細を読む...
「サポート対象プラットフォーム」ページで、アップグレード先の Bitbucket バージョンを確認します。ここでは、サポート対象のオペレーティング システム、データベース、およびブラウザを確認できます。
|
Have you modified your server.xml file? |
詳細を読む...
Bitbucket 5 で、ポート番号、コンテキスト パス、アクセス プロトコルなどのプロパティの設定場所を変更して単一のディレクトリおよびファイルにまとめ、以降のリリースでのアップグレードを行いやすくしました。 Bitbucket 4.14 以前の任意のバージョンから Bitbucket 5.0 以降にアップグレードする場合、 See the page Migrate customizations from
|
アップグレードを計画する
1. アップグレード パスを決定する
You can update from any previous version of Bitbucket Server (or Stash) to the latest version, as there is no required upgrade path.
Bitbucket 7 is a major upgrade
Be sure to read the Bitbucket Server 7.0 release notes, take a full backup, and test your upgrade in a non-production environment before upgrading your production site.
Bitbucket 7 よりも古いバージョンからアップグレードすると、ユーザーがインストールしたすべてのアプリが起動時に無効化されます
Be sure to update your own apps and check the Atlassian Marketplace to ensure 3rd-party apps are compatible with Bitbucket Server 7 before upgrading.
次のバグ修正アップデートへのアップグレード
複数ノードの Bitbucket クラスタを次のバグ修正アップデートにアップグレードする場合 (7.9.0 から 7.9.4 など)、ダウンタイムなしでアップグレードできます。
2. Complete pre-upgrade checks
- アップグレード先として計画しているバージョン (およびその間のバージョン) のバージョンごとのアップグレード ノートを確認します。
> [サポート ツール] に移動し、解決が必要な問題がログ アナライザーにあるかどうかを確認します。
Check the compatibility of your apps with the version you plan to upgrade to.
> [アプリの管理] > [Bitbucket 更新の確認] に移動します。
アップグレード先として計画しているバージョンを選択して [確認] を押します。
If you have incompatible appsIf your users rely on particular apps, you may want to wait until they are compatible before upgrading Bitbucket. App vendors generally update their apps very soon after a major release.
参考情報
- Bitbucket Server 6 よりも古いバージョンからアップグレードすると、ユーザーがインストールしたすべてのアプリが自動的に無効になります。Bitbucket Server 6 との互換性の有無にかかわらず、アップグレードが正常に完了したらアプリを有効にする必要があります。
- You can disable an app temporarily if it is not yet compatible.
3. Upgrade Bitbucket in a test environment
- Create a staging copy of your current production environment.
- 以下の手順に従って、テスト環境をアップグレードします。
- Test any unsupported apps, customizations and proxy configuration (if possible) before upgrading your production environment.
Upgrade Bitbucket
This upgrade process does not perform an in-place upgrade, but instead installs the new version of Bitbucket Server into a new installation directory. The new instance uses your existing Bitbucket Server home directory and external database.
If necessary, rolling back an upgrade can only be performed by restoring a backup of both the Bitbucket Server home directory and the Bitbucket Server database – rolling back requires a consistent home directory and database. You can then reinstall the previous version of the application to the installation directory. Read the Rollback section for more details.
4. Download Bitbucket Server
Download the installer (the recommended approach) for your operating system - www.atlassian.com/software/bitbucket/download.
5. データをバックアップする
Determine which backup strategy to use.
Summary of the different backup strategies for Bitbucket...For Bitbucket Server (version 4.8 or later) instances, you can use Zero Downtime Backup, the Backup Client (version 2.7 or later), or DIY Backup (version 2.12 or later) while Bitbucket is running, or just stop Bitbucket and zip up / snapshot the home directory and database and keep them somewhere safe.
For Bitbucket Data Center (version 4.8 or later) instances, you can use Zero Downtime Backup, DIY Backup, or take snapshots of the shared home directory (on NFS) and database while all nodes are stopped.
For Bitbucket mirrors, the home directory doesn't store any persistent state that can't be reconstructed from the primary Bitbucket instance, but you should still make sure you have a backup of at least the important configuration files such as SSL certificate,
server.xml
,config/ssh-server-keys.pem
,bitbucket.properties
file, and so on in a safe place. See How do I back up my mirrors? for more information.See the article Data recovery and backups for detailed information and guidance on creating an effective backup strategy.
- Back up all the data in your Bitbucket home directory and external database.
6. Migrate customizations
Bitbucket 5 以降では、サーバーのカスタム構成は異なる場所に保存されています。これまでは、Tomcat コンテナのカスタマイズ設定は server.xml
で行い、<Bitbucket home directory>
/shared
ディレクトリ (3.8 から 4.14)、または <Stash installation directory>/
conf
(3.7 以前) に保存していました。
Bitbucket 4.14 以前からアップグレードする場合に必要な手順
First, determine if you've made customizations to your
server.xml
file. You would have made these changes if you modified the port, context path, or the access protocol, or if you are running Bitbucket Server behind a proxy and modified the Connector element.Help me find my server.xml file...Release ディレクトリ Stash 3.7 and earlier <Stash installation directory>/
conf/server.xml
Stash 3.8 and later <Stash home directory>
/shared/server.xml
Bitbucket Server 4.0 - 4.14 <Bitbucket home directory>
/shared/server.xml
Bitbucket Server 5.0 and later N/A, replaced by <Bitbucket home directory>
/shared/bitbucket.properties
If you made any customizations to the
server.xml
file, you must migrate those changes in thebitbucket.properties
file in your existing Bitbucket home directory. Thebitbucket.properites
file uses a slightly different syntax, so it is not merely a copy and paste procedure.
Read the page Migrate customizations fromserver.xml
tobitbucket.properties
and follow the instructions to migrate your customizations. Once your changes are migrated, proceed to the next step.
If you did not make any customizations to theserver.xml
file, proceed to the next step.For custom configurations in Bitbucket Data Center...Bitbucket Data Center instances on version 3.8 or later, the single
server.xml
file in the<Bitbucket home directory>
/shared
directory replaces all the copies ofserver.xml
located in the<Bitbucket installation directory>/conf
directories of the cluster nodes using previous versions of Bitbucket Server (or Stash).
7. Stop the application
To stop Bitbucket Server from the interface, use the Bitbucket Server items in the Windows Start menu.
To stop Bitbucket Server from a command prompt, change directories to the <Bitbucket Server installation directory>
and run this command:
bin\stop-bitbucket.bat
To stop Bitbucket Server when running as a service, stop the Bitbucket Server service from the Windows services console.
To stop Bitbucket Server from a terminal, change to the <Bitbucket Server installation directory>
and run:
bin/stop-bitbucket.sh
Be sure to stop all nodes of Bitbucket Data Center, perform the steps to upgrade for a single node first, then repeat the process on each cluster node.
詳細な手順については「Bitbucket の開始と終了」ページをご確認ください。
8. インストーラーを実行する
You can run the installer in GUI, console or unattended modes.
インストーラーを実行します。
Windows で実行する場合....exe ファイルを実行します。Windows 管理者アカウントを使用することをおすすめします。
Linux で実行する場合...Change to the directory where you downloaded Bitbucket Server then execute this command to make the installer executable:
chmod +x atlassian-bitbucket-x.x.x-x64.bin
sudo
を使用してインストーラーを実行することをお勧めします。これにより Bitbucket Server を実行する専用アカウントが作成され、Bitbucket Server をサービスとして実行できます。インストーラーを実行するために
sudo
を使用するには、次のコマンドを実行します。$ sudo ./atlassian-bitbucket-x.x.x-x64.bin
You can also run the installer with root user privileges.
- Follow the prompts to upgrade Bitbucket Server.
At the 'Welcome' step, choose the type of instance to upgrade
Help me decide which type of upgrade to choose...For a single node (most users), choose the Upgrade an existing Bitbucket instance option.
For Bitbucket Data Center instances, choose the Upgrade an existing Bitbucket instance option, and repeat the upgrade process for each application node.
For a Bitbucket mirror, choose the Upgrade an existing mirror option.At the 'Select Bitbucket Server Home' step, select your existing home directory.
Proceed with the remaining installer steps.
9. Start the application
If you’re also upgrading your operating system libraries and using PostgresSQL and glibc version lower than 2.28, and the upgrade increases the glibc version to 2.28 or later, you’ll need to rebuild the PostgresSQL indices before starting Bitbucket.
When using the installer, there will be an option to start the application (and launch it in a browser) at the end of the installation wizard.
Bitbucket を手動で開始する方法を含む詳細な手順については、「Bitbucket の開始と終了」をご確認ください。
Rollback
If necessary, rolling back an update can only be performed by restoring a backup of both the Bitbucket Server home directory and the Bitbucket Server database – rolling back requires a consistent home directory and database. You can then reinstall the previous version of the application to the installation directory. Never start an older binary against an upgraded home directory.
Version-specific update notes
このセクションでは、Bitbucket Data Center および Server のそれぞれのバージョン固有のアップデート ノートを案内します。ノートの記載内容は、上述の主要なアップグレード手順を補足するものです。アプリケーションの現在のバージョンとアップグレード先のバージョンとの間の各バージョンについて、関連するセクションをご確認ください。
Bitbucket Data Center および Server 7.15 アップデート ノート
You should also see:
- the general Upgrade steps section above.
- Bitbucket Data Center および Server 7.15 リリース ノート。
- the Bitbucket Server Supported platforms page.
- サポート終了についてのお知らせ
Bitbucket Data Center および Server 7.14 アップデート ノート
You should also see:
- the general Upgrade steps section above.
- Bitbucket Data Center および Server 7.14 リリース ノート。
- the Bitbucket Server Supported platforms page.
- サポート終了についてのお知らせ
Bitbucket Data Center および Server 7.13 アップデート ノート
You should also see:
- the general Upgrade steps section above.
- Bitbucket Data Center および Server 7.13 リリース ノート。
- the Bitbucket Server Supported platforms page.
- サポート終了についてのお知らせ
Bitbucket Data Center および Server 7.12 アップデート ノート
You should also see:
- the general Upgrade steps section above.
- Bitbucket Data Center および Server 7.12 リリース ノート。
- the Bitbucket Server Supported platforms page.
- サポート終了についてのお知らせ
Bitbucket Data Center および Server 7.11 アップデート ノート
You should also see:
- the general Upgrade steps section above.
- Bitbucket Data Center および Server 7.11 リリース ノート。
- the Bitbucket Server Supported platforms page.
- サポート終了についてのお知らせ
Bitbucket Data Center および Server 7.10 アップデート ノート
You should also see:
- the general Upgrade steps section above.
- Bitbucket Data Center および Server 7.10 リリース ノート。
- the Bitbucket Server Supported platforms page.
- サポート終了についてのお知らせ
Bitbucket Server 7.9 update notes
You should also see:
- the general Upgrade steps section above.
- Bitbucket Server および Data Center 7.9 リリース ノート。
- the Bitbucket Server Supported platforms page.
- サポート終了についてのお知らせ
Bitbucket Server 7.8 update notes
You should also see:
- the general Upgrade steps section above.
- Bitbucket Server および Data Center 7.8 リリース ノート。
- the Bitbucket Server Supported platforms page.
- サポート終了についてのお知らせ
Bitbucket Server 7.7 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 7.7 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 7.6 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 7.6 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 7.5 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 7.5 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 7.4 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 7.4 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
New Data Center apps check as part of your license upgrade
Bitbucket Data Center ライセンス へのアップグレードに、アプリのチェック機能が新しく追加されました。インストール済みのアプリに Data Center 認定バージョンへのアップグレードが必要なものがあれば、新しい Bitbucket ライセンスの適用前にその旨を確認できます。
また、管理コンソールの [アプリの管理] セクションに新しいステータス メッセージを追加し、新しいライセンスが必要なアプリを明確に確認できるようにしました。
New status | Host product license | 意味 |
---|---|---|
DATA CENTER LICENSE AVAILABLE | Evaluation license | The app vendor offers a Data Center version of this app. If you switch to a paid Data Center product license, you’ll need to upgrade this app license to Data Center. |
LICENSE INCOMPATIBLE | Full license | The app vendor offers a Data Center version of this app. Your Server app license is no longer compatible with the product. This means the app has either stopped working, or functionality has been lost or compromised. You need to add a Data Center license. |
Data Center への移動後に Server アプリをアップグレードする方法の詳細をご確認ください。
Build status data migration
When upgrading to Bitbucket Server 7.4, you may notice an increased load on your database and application server. This is normal. It’s due to an asynchronous upgrade task that needs to run to migrate your application’s build status data.
While the upgrade task is running, your application will be available and able to serve requests, so your team can continue working as usual.
The upgrade task will run automatically around two minutes after your application starts up. In a multi-node cluster, it will run on a node picked by the system. How long it takes will depend on the size of the data that needs to be migrated. For example, for small instances it can take 10 minutes, and for large instances it can take over an hour.
Bitbucket Server 7.4 にアップグレードする前に、本番環境のセットアップをミラーリングしたステージング環境で HTTP ホスティングをテストする必要があります。これには特にインストール済みのアプリが含まれます。これは、アプリが提供するサーブレットが非同期の HTTP によって破損する可能性があるためです。
Bitbucket Server 7.3 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 7.3 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 7.2 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 7.2 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 7.1 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 7.1 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 7.0 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 7.0 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket 7.0 以降へのアップグレードを検討していて、Bitbucket branch source
Jenkins プラグインのバージョン 2.8 以前を使用している場合、これによってビルドが失敗する既知の問題があります。これは、プル リクエストへの変更は継続的に発生するが、マージの処理が断続的に行われるためです。
詳細については BSERV-12284 - Getting issue details... STATUS をご確認ください。
Bitbucket Server 6.10 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.10 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.9 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.9 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.8 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.8 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.7 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.7 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.6 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.6 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.5 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.5 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.4 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.4 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.3 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.3 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.2 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.2 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.1 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.1 release notes.
- the Bitbucket Server Supported platforms page.
- サポート終了のお知らせ。
Bitbucket Server 6.0 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 6.0 release notes.
- the Bitbucket Server Supported platforms page.
- the End of support announcements for Bitbucket Server.
To upgrade to Bitbucket Server 5+, you must migrate customizations to bitbucket.properties
Be sure to carefully read the Bitbucket Server upgrade guide to determine what impact this change may have on your instance. The page Migrate server.xml
customizations to bitbucket.properties
has specifics on which properties need to be migrated, how to migrate them, and includes some examples that demonstrate how to migrate some common customizations.
Start script changes
Bitbucket Server 5.0 以前では、一部の開始スクリプトの名前がアンダースコアで開始されていました。これらのスクリプトは廃止されたため、直接呼び出すことはできません。これは、複数の開始および停止スクリプトがあり、使用する際に混乱が生じていたためです。現在は、start
で開始するスクリプトと、stop
で開始するスクリプトのみが提供されています。
既知の問題
Bitbucket Server 5.16 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.16 release notes.
- the Bitbucket Server Supported platforms page.
- the End of support announcements for Bitbucket Server.
Bitbucket Server 5.15 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.15 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.14 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.14 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.13 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.13 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.12 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.12 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.11 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.11 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.10 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.10 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.9 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.9 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.8 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.8 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.7 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.7 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.6 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.6 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.5 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.5 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.4 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.4 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.3 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.3 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.2 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.2 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.1 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.1 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
Bitbucket Server 5.0 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 5.0 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
To upgrade to Bitbucket Server 5+, you must migrate customizations to bitbucket.properties
Be sure to carefully read the Bitbucket Server upgrade guide to determine what impact this change may have on your instance. The page Migrate server.xml
customizations to bitbucket.properties
has specifics on which properties need to be migrated, how to migrate them, and includes some examples that demonstrate how to migrate some common customizations.
Start script changes
In Bitbucket Server 5.0, some startup scripts have had their name prefixed with an underscore. These scripts have been deprecated, and you should no longer call these scripts directly. This is to avoid confusion, because previously there were multiple start and stop scripts, making it easy to confuse which one to call. Now, there is only one script, that begins with "start
" and one that begins with "stop
".
BitbucketServer does not support reverse proxies using AJP connections
Starting from version 5.0, Bitbucket Server does not support reverse proxies using AJP connections. While never officially supported, previous versions of Bitbucket Server could use AJP connections. However, with changes to how Bitbucket Server uses Tomcat, using AJP connections with Bitbucket Server (or Data Center) 5.0+ will cause the application to fail on startup.
既知の問題
Bitbucket Server 4.14 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.14 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- Bitbucket Server のサポート終了のお知らせ。
既知の問題
Bitbucket Server 4.13 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.13 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.12 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.12 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
Do NOT upgrade to Git 2.11+
Any version after Git 2.11.0 (including future 2.12+ releases) cannot be used with Bitbucket Server. Bitbucket Server 4.12 will fail on startup if Git 2.11+ is detected. Only upgrade to versions of Git which are explicitly marked supported on our Supported Platforms page.
BSERV-9388 - Getting issue details... STATUS
既知の問題
Bitbucket Server 4.11 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.11 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.10 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.10 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.9 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.9 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.8 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.8 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.7 update notes
You should also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.7 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.6 update notes
Also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.6 release notes.
- Stash のサポート対象プラットフォーム ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.5 update notes
Also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.5 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.4 update notes
Also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.4 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.3 update notes
Also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.3 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.2 update notes
Also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.2 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.1 update notes
Also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.1 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。
既知の問題
Bitbucket Server 4.0 update notes
Also see:
- the general Upgrade steps section above.
- the Bitbucket Server 4.0 release notes.
- Bitbucket Server の「サポート対象プラットフォーム」ページ。
- サポート終了のお知らせ。Bitbucket Server 4.0 では、Internet Explorer 9 または 10、Java 7、バージョン 1.8 より前のサーバー版 Git がサポートされない点にご注意ください。
Do you rely on user-installed add-ons?
Your plugins may not be compatible with Bitbucket Server 4.0 (yet)
Upgrading from Stash to Bitbucket Server will disable all user-installed add-ons, whether they are 3rd-party add-ons from Atlassian Marketplace, or your own custom add-ons. User-installed add-ons will need to be checked, upgraded and enabled again once you've finished the upgrade process. You should check the marketplace listing for 3rd-party add-ons to determine if there is a release that is compatible with Bitbucket Server 4.0. Unless they have been updated to work with Bitbucket Server 4.0, existing add-ons (or plugins) that use the API interfaces that have been removed in Bitbucket Server 4.0 will not work. Similarly, custom add-ons need to be upgraded for Bitbucket Server compatibility. See the documentation on how to update your add-on for details.
If you are upgrading from Stash 3.x to Bitbucket Server 4.x, you should be aware that most user-installed add-ons will be incompatible with Bitbucket Server 4.0. After upgrading, go to Admin > Manage add-ons, look for messages of this form, and follow the advice to update:
If no newer version is available the add-on will remain disabled.
New dedicated user account 'atlbitbucket'
A new dedicated user account will be created to run Bitbucket Server, called atlbitbucket
. During the upgrade process, you will have an option to delete the dedicated user account for running Stash, named atlstash
. For most users, deleting this dedicated user account won't have any negative consequences, however if you rely on this dedicated user accounts, for example in custom backup scripts, you will need to update the user account in those scripts.
Updates to logger names
If you have customized your logging configuration by manually editing the logback.xml
file (using steps found in the Configure Stash Logging KB article), you should be aware of changes to several logger names that may require you to update some of your configuration files.
Stash logger name | Bitbucket Server logger name |
---|---|
stash.application | bitbucket.application |
stash.profiler | bitbucket.profiler |
stash.access-log | bitbucket.access-log |
stash.audit-log | bitbucket.audit-log |
stash.mail-log | bitbucket.mail-log |
Important security improvement which may require configuration changes
Previous to Bitbucket Server 4.0, a security constraint for redirecting from HTTP to HTTPS was not enforced, meaning users could type "http://<bitbucketserver-url>" into their browser and still be shown a functioning version of Bitbucket Server (or Stash). Included with the release of Bitbucket Server 4.0 was a fix to enforce that security constraint. Using the previous security configuration with Bitbucket Server 4.0 means trying to access the application over an insecure connection, when users type "http" when trying to get to the application, they could encounter erroneous behavior.
As part of upgrading from Stash to Bitbucket Server, it is recommended you update your security configuration in order to avoid encountering this problem. See this Knowledge Base article for more information and specific instructions on addressing this: Redirect HTTP Requests to HTTPS.
既知の問題
Stash 3.11 update notes
Also see:
- the general Upgrade steps section above.
- the Stash 3.11 release notes.
- the Stash Supported platforms page. Note that Stash 3.11 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。Stash 4.0 では Internet Explorer 9 または 10、Java 7、バージョン 1.8 より前のサーバー版 Git がサポートされなくなる点に特にご注意ください。
- If you have installed the stash-stream-guard-plugin (for example, if advised to do so by Atlassian Support), then you should uninstall it when upgrading to 3.11.2 as its functionality is now bundled in Stash.
既知の問題
Stash 3.10 update notes
Also see:
- the general Upgrade steps section above.
- the Stash 3.10 release notes.
- the Stash Supported platforms page. Note that Stash 3.10 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。Stash 4.0 では Internet Explorer 9 または 10、Java 7、バージョン 1.8 より前のサーバー版 Git がサポートされなくなる点に特にご注意ください。
Are you using Git 2.2x - 2.4.0?
Git 2.2.x - 2.4.0 have reported performance issues when interacting with NFS. Hence, these versions are currently not supported for Stash Data Center or for Stash Server installations that use NFS mounts for the home directory.
既知の問題
Stash 3.9 update notes
Also see:
- the general Upgrade steps section above.
- the Stash 3.9 release notes.
- the Stash Supported platforms page. Note that Stash 3.9 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。Stash 4.0 では Internet Explorer 9、Java 7、バージョン 1.8 より前のサーバー版 Git がサポートされなくなる点に特にご注意ください。
Are you using JIRA as a Crowd server?
Stash 3.9 cannot use JIRA 6.4 as a Crowd server due to a bug in JIRA 6.4. Please upgrade to JIRA 6.4.1 before upgrading Stash. (Note that Stash 3.7.2 and 3.8.0 contained a workaround for the bug but the workaround was removed in Stash 3.9)
既知の問題
Stash 3.8 update notes
Also see:
- the general Upgrade steps section above.
- the Stash 3.8 release notes.
- the Stash Supported platforms page. Note that Stash 3.8 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。Stash 4.0 では Internet Explorer 9、Java 7、バージョン 1.8 より前のサーバー版 Git がサポートされなくなる点に特にご注意ください。
Have you made customizations to Tomcat's server.xml
file?
For Stash 3.8 (and future versions) the server.xml
file is now located in the <stash home directory>/shared
directory. The benefit of this move is that your customizations to server.xml
will not have to be redone for future upgrades.
You still need to update your custom configurations in
shared/server.xml
for the upgrade to Stash 3.8.
Deprecation of HighlightJS for syntax highlighting
The highlighting engine was changed in Stash 3.5 from HighlightJS to CodeMirror. The use of HighlightJS for syntax highlighting in Stash is now deprecated, and will be removed in Stash 4.0. See Syntax highlight changes for information about how to migrate any custom mappings for HighlightJS that you may have made.
既知の問題
Stash 3.7 update notes
Also see:
- the general Upgrade steps section above.
- the Stash 3.7 release notes.
- the Stash Supported platforms page. Note that Stash 3.7 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。Stash 4.0 では Internet Explorer 9、Java 7、バージョン 1.8 より前のサーバー版 Git がサポートされなくなる点に特にご注意ください。
Do you use JIRA 6.4?
JIRA 6.4 has a known issue with Stash versions 3.4.3 to 3.7.1, which prevents the user synchronization from working. This will only affect you if you use JIRA to manage your users in Stash, and is fixed in Stash 3.7.2.
Deprecation of HighlightJS for syntax highlighting
The highlighting engine was changed in Stash 3.5 from HighlightJS to CodeMirror. The use of HighlightJS for syntax highlighting in Stash is now deprecated, and will be removed in Stash 4.0. See Syntax highlight changes for information about how to migrate any custom mappings for HighlightJS that you may have made.
既知の問題
Stash 3.6 update notes
Also see:
- the general update steps section above.
- the Stash 3.6 release notes.
- the Stash Supported platforms page. Note that Stash 3.6 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。Stash 4.0 では Internet Explorer 9、Java 7、バージョン 1.8 より前のサーバー版 Git がサポートされなくなる点に特にご注意ください。
Secure email notifications
Stash 3.6 now:
- Allows you to require STARTTLS support on the mail server when using SMTP – if it is not supported, mail is not sent.
- Supports SMTPS (where the whole protocol conversation uses SSL/TLS).
See Setting up your mail server for more information.
Note that if you use either SMTP with STARTTLS or SMTPS and connect to a self-signed mail server you may need to import the server's certificate and set up a custom cacerts file for Stash (just as you do for any outbound SSL/TLS connection to a self-signed server). See this Stash knowledge base article for information about how to do that.
Deprecation of HighlightJS for syntax highlighting
The highlighting engine was changed in Stash 3.5 from HighlightJS to CodeMirror. The use of HighlightJS for syntax highlighting in Stash is now deprecated, and will be removed in Stash 4.0. See Syntax highlight changes for information about how to migrate any custom mappings for HighlightJS that you may have made.
既知の問題
Stash 3.5 update notes
Also see:
- the general update steps section above.
- the Stash 3.5 release notes.
- the Stash Supported platforms page. Note that Stash 3.5 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。Stash 4.0 では Java 7、バージョン 1.8 より前のサーバー版 Git がサポートされなくなる点に特にご注意ください。
Stash home directory location
Stash 3.5 以降のバージョンでは、ホーム ディレクトリを Stash のインストール ディレクトリと同じ場所にしたり、Stash のインストール ディレクトリのサブディレクトリにしたりすることはできません。Stash のホーム ディレクトリは STASH_HOME
環境変数で定義され、別の場所に存在する必要があります。これに違反する場合、Stash は開始に失敗します。
Deprecation of HighlightJS for syntax highlighting
The highlighting engine in Stash has been changed from HighlightJS to CodeMirror. The use of HighlightJS for syntax highlighting in Stash is now deprecated, and will be removed in Stash 4.0. See Syntax highlight changes for information about how to migrate any custom mappings for HighlightJS that you may have made.
既知の問題
Stash 3.4 update notes
Also see:
- the general update steps section above.
- the Stash 3.4 release notes.
- the Stash Supported platforms page. Note that Stash 3.4 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。
Changed group membership aggregation with multiple user directories
Stash 3.4 uses new schemes to determine the effective group memberships when Stash is connected to multiple user directories, and duplicate user names and group names are used across those directories. The new schemes are:
- 'aggregating membership'
- 'non-aggregating membership'.
These group membership schemes are only used to determine authorization. Authentication is determined on the basis of the group mappings in each directory.
See Effective memberships with multiple directories in the Crowd documentation for more information.
When you update to Stash 3.4, an update task will apply one of those schemes as follows:
Aggregating membership will be applied to your instance:
- If there is only one active directory.
- If there are multiple active directories but only a single directory applies group memberships to any particular user.
- For example, if directory-1 contains user-a in group-x, and directory-2 contains user-b in group-y, then Stash 3.4 will apply aggregating membership, and permissions will not be affected.
Non-aggregating membership will be applied to your instance:
- If there are multiple active directories and more than one directory applies group memberships to at least one user.
- For example, if directory-1 contains user-a in group-x, and directory-2 contains user-a in group-y, then Stash 3.4 will apply non-aggregating membership. If group-y has admin provileges then user-a would have their privileges escalated in this case if aggregating membership was applied instead when upgrading to Stash 3.4.
Any changes made by the update task will be logged.
A Stash admin can change the membership scheme used by Stash using the following commands:
To change to aggregating membership, substitute your own values for
<username>
,<password>
and<base-url>
in this command:curl -H 'Content-type: application/json' -X PUT -d '{"membershipAggregationEnabled":true}' -u <username>:<password> <base-url>/rest/crowd/latest/application
To change to non-aggregating membership, substitute your own values for
<username>
,<password>
and<base-url>
in this command:curl -H 'Content-type: application/json' -X PUT -d '{"membershipAggregationEnabled":false}' -u <username>:<password> <base-url>/rest/crowd/latest/application
Note that changing the aggregation scheme can affect the authorization permissions for your Stash users, and how update operations are performed. Read more about using Stash with multiple use directories.
既知の問題
Stash 3.3 update notes
Also see:
- the general update steps section above.
- the Stash 3.3 release notes.
- the Stash Supported platforms page. Note that Stash 3.3 does not support Git 2.0.2 or 2.0.3.
- サポート終了のお知らせ。
既知の問題
Stash 3.2 update notes
Upgrading to Stash 3.2 or later from Stash 3.1 or earlier is irreversible – please see the Home directory migration section below.
Also see:
- the general update steps section above.
- the Stash 3.2 release notes.
- the Stash Supported platforms page.
- サポート終了のお知らせ。
注意:
- Stash 3.2 does not support Git 2.0.2 or 2.0.3.
Home directory migration
When you update to Stash 3.2 or later, an update task migrates directories in your Stash home directory to new locations. This is irreversible – once you update to Stash 3.2 or later you can not revert to Stash 3.1 or earlier, because of changes to the Stash home directory format.
For most installations, Stash 3.2 is able to perform these moves automatically and transparently. However, in the rare instance where Stash 3.2 can't perform the update automatically, please refer to Upgrading your Stash home directory for Stash 3.2 manually.
Undocumented home directory overrides are no longer supported
Before Stash 3.2 it was possible to override the location of the following subfolders in the Stash home directory, using undocumented environment variables or system properties:
export
bin
caches
config
data
lib
lib/native
log
plugins
tmp
tmp
サブフォルダのみとなります。その他のオーバーライドを試みた場合、開始時に失敗します。詳細については、「Stash の開始に失敗 - UnsupportedDirectoryOverrideException」をご参照ください。 Stash analytics
Stash 3.2 以降は、ユーザーのイベント データを収集します (管理者によって無効化されている場合を除く)。これにより、amazonaws.com への出力ネットワークが発生します。「データ収集設定の変更」をご確認ください。
既知の問題
Stash 3.1 update notes
Also see:
- the general update steps section above.
- the Stash 3.1 release notes.
- the Stash Supported platforms page.
注意:
既知の問題
Stash 3.0 update notes
Stash no longer supports Java 6
Stash 3.0 requires at least Java 7, and supports Java 8.
「サポート終了のお知らせ」をご確認ください。
Your plugins may not be compatible with Stash 3.0
The interfaces in the Stash API for plugin developers that were deprecated in Stash 2.11 and earlier have been removed in Stash 3.0. This means that, unless they have been updated to work with Stash 3.0, existing Stash add-ons (or plugins) that use these interfaces will not work with Stash 3.0.
Please see the section below about Stash add-on incompatibilities for more details.
Also see:
- the general update steps section above.
- the Stash 3.0 release notes.
- the Stash Supported platforms page.
注意:
- Stash now has installers for the Linux, macOS and Windows platforms.
- Stash no longer supports Internet Explorer 8, as previoiusly announced.
- Stash では Apache HTTP Server の
mod_auth_basic
モジュールはサポートされません。 - Stash does not support Git 2.0.2 or 2.0.3.
Stash add-on incompatibilities
Unless they have been updated to work with Stash 3.0, existing Stash add-ons (or plugins) that use the API interfaces that have been removed in Stash 3.0 will not work.
Fresh installs of Stash 3.0 shouldn't encounter any problems. The Stash 'Manage add-ons' page (in the admin area) should only display add-ons from the Marketplace that have been marked as compatible with Stash 3.0. Incompatible add-ons won't be available in the list.
However, if you are upgrading from Stash 2.x to Stash 3.0, you should be aware that some existing installed add-ons may be incompatible with Stash 3.0. After upgrading, you should go to Admin > Manage add-ons, look for messages of this form, and follow the advice to update:
If no newer version is available, the add-on must be disabled.
Custom add-ons
Please note that your custom locally-developed plugins may be affected by the API removals in Stash 3.0. You will need to update your custom plugins if you want those to work with Stash 3.0. See the Stash API changelog for details of the deprecated APIs.
他社製アドオン
You'll need to check on Atlassian Marketplace for the compatibility status of any 3rd-party add-ons that you use.
サードパーティ アドオンの開発者には、リリースに先立って Stash 3.0 のアーリー アクセス プログラム (EAP) ビルドが提供されており、ほとんどの開発者が互換性を保つようにアドオンをすでに更新しています。Stash の [アドオンの管理] ページにアドオンが表示されるようにするには、公開元が Stash 3.0 との互換性を明示的にマークしている必要があります。これは 2.10 や 2.11 などの過去のマイナー リリースのように自動的に行われるわけではありません。アトラシアンでは、Stash 3.0 との互換性を持たないサードパーティ アドオンに関連する問題をサポートすることはできません。このようなサポート ケースはアドオンのサードパーティの公開元で扱う必要があります。「アプリの管理」をご確認ください。
Atlassian add-ons
All of the Atlassian add-ons for Stash that are available from the Atlassian Marketplace have been updated to be compatible with Stash 3.0. If you use any of these in your Stash installation you'll need to update them to the Stash 3.0 compatible version.
Add-on | JAR file name | Stash 3.0 compatible version |
---|---|---|
Custom Navigation Plugin | custom-navigation-plugin | 2.0.3 |
Stash Archive Plugin | stash-archive | 1.3.0 |
Repository git operations plugin | stash-git-ops-plugin | 1.2.1 |
Stash Auto Unapprove Plugin | stash-auto-unapprove-plugin | 1.1 |
Stash Protect Unmerged Branch Hook | stash-protect-unmerged-branch-hook | 1.1 |
Stash Reviewer Suggester | stash-suggest-reviewers | 1.2 |
Stash Web Post Hooks Plugin | stash-web-post-receive-hooks-plugin | 1.1.0 |
Realtime Editor for Stash | stash-editor-plugin | 1.0.6 |
既知の問題
Stash 2.12 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。特に、Java 6 のサポートは廃止予定である点にご注意ください。Stash 3.0+ では Java 7 が必要になります。
- the Stash 2.12 release notes.
注意:
- Stash does not yet support Java 8.
- Stash 2.12 does not support Git 1.8.4.3
- Stash では Apache HTTP Server の
mod_auth_basic
モジュールはサポートされません。
See Supported platforms.
既知の問題
Stash 2.11 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。
- the Stash 2.11 release notes.
Note that Stash does not support Git 1.8.4.3, nor does Stash support Java 8 yet. See Supported platforms.
既知の問題
Stash 2.10 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。
- the Stash 2.10 release notes.
Note that Stash does not support Git 1.8.4.3. See Supported platforms.
既知の問題
Stash 2.9 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。
- the Stash 2.9 release notes.
Note that Stash does not support Git 1.8.4.3. See Supported platforms.
Pull Request Ref Optimization
Stash 2.9 へのアップグレード後に最初に Stash を起動すると、Stash が管理するすべてのリポジトリ用にプル リクエストの ref を最適化する、リポジトリのアップグレード タスクが実行されます。このアップグレード プロセスを中断しないでください。これらの進捗は Stash のログで追跡できます。 STASH-3469 - Getting issue details... STATUS をご確認ください。
Backup Client Update Required
Version 1.0.3 of the Stash Backup Client is required to back up Stash 2.9.
既知の問題
Stash 2.8 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。
- the Stash 2.8 release notes.
既知の問題
Stash 2.7 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。
Repository System Information Plugin is now deprecated
The functionality of the repository system information plugin has now been moved into core Stash. The plugin will still work for Stash 2.x versions but is redundant as of Stash 2.7.
MySQL default isolation level
Stash 2.7.x uses READ_COMMITTED instead of the MySQL default isolation level (REPEATABLE_READ). This can result in exceptions when installing or upgrading to 2.7.x, if binary logging is enabled in your MySQL server. More details and a fix can be found in this KB article.
既知の問題
Stash 2.6 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。
既知の問題
Stash 2.5 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。
既知の問題
Limited support for JIRA 4.4.x and earlier
JIRA 4.3+ allows for showing commits associated with issues in JIRA. However, viewing issues within Stash is not supported for JIRA 4.4.x and earlier.
Stash 2.4 update notes
Also see:
- the update steps section above.
- サポート終了のお知らせ。
既知の問題
Stash 2.3 update notes
Please also see the update steps section above.
When upgrading to Stash 2.3 you also need to update the SCM Cache plugin, due to recent Stash API changes.
既知の問題
Stash 2.2 update notes
Please see the update steps section above.
既知の問題
Stash 2.1 update notes
Please also see the update steps section above.
既知の問題
Install location for third-party libraries
Stash 2.1 以降では、MySQL JDBC ドライバなどのサードパーティ製のライブラリや jar ファイルを、<Stash home directory>/lib
にインストールできます。ここにあるファイルは、Stash の更新時に上書きされたり、失われたりすることはありません。
Microsoft SQL Server JDBC driver
Stash 2.1 now uses the Microsoft SQL Server JDBC driver to access Microsoft SQL Server, instead of using the jTDS driver. In most cases, Stash will automatically swap to using the Microsoft driver on update and no configuration is required.
If Stash was configured to use Microsoft SQL Server by manually entering a JDBC URL, please refer to this guide.
Stash 2.0 update notes
This section provides specific notes for upgrading to Stash 2.0. See also the update steps section above.
Tomcat
Stash 2.0 では、Tomcat がバージョン 6 から 7 に更新されました。この更新の一環として、 server.xml
ファイルが変更されました。server.xml
ファイルをカスタマイズしている場合 (例: port
、path
、または hostname
)、現在のバージョンを更新された Stash に単純にコピーすることはできません。カスタマイズ内容を新しいバージョンの Stash の server.xml
に再適用する必要があります。
If you were running Stash as a Windows service and are upgrading from 1.x to 2.x you will need to reinstall the Stash service to make it use Tomcat 7.
To uninstall the Stash service you need to execute following commands from <STASH DISTRIBUTION DIR>\bin:
> net stop <service name>
> service.bat uninstall <service name>
You can call this command without the service name if you installed the Stash service with a default name.
After the service is uninstalled you can proceed with the update steps and Running Bitbucket Server as a Windows service instructions to configure Stash 2.x running as a service.
Perl
Stash 2.0 requires Perl for its branch permission functionality. If Perl is unavailable, Stash 2.0 will not start.
On Windows machines, Perl will only have been installed by the Git installer if the correct install option was chosen. See Installing and upgrading Git.
Existing Git hooks
ブランチ権限をサポートするため、Stash 2.0 は <Stash home directory>/data/repositories/NNNN/hooks
(ここで NNN は内部のリポジトリ ID) の pre-receive
および post-receive
フォルダにある既存のフックを .../hooks/pre-receive.d/10_custom
または .../hooks/post-receive.d/10_custom
に移動します。これにより、相対パス名 (例: "./foo.sh" または "../dir/foo.sh") を使用するカスタム フックは Stash 2.0 への更新で壊れます。
Deprecation of Internet Explorer 8
Support for Internet Explorer 8 is deprecated from the release of Stash 2.0. The official end-of-support date is yet to be determined. See Supported platforms for details.
既知の問題
Check for known issues and troubleshooting
If something is not working correctly after you have completed the steps above to update your Stash installation, please check for known Stash issues and try troubleshooting your update as described below:
- Check for known issues. Known issues can be seen in the BSERV project on our issue tracker.
- Bitbucket Server Knowledge Base. Sometimes we find out about a problem with the latest version of Stash after we have released the software. In such cases we publish information in the Bitbucket Server Knowledge Base.
- If you encounter a problem during the update and cannot solve it, please create a support ticket and one of our support engineers will help you.
このセクションの項目
関連コンテンツ
- 関連コンテンツがありません