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?

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

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:

In Stash 3.2 only the  tmp  subfolder can be overridden in this way. Attempting to override the others will fail on startup. For more information, please see  Stash fails to start - 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 does not support Git 2.0.2 or 2.0.3.

既知の問題

Stash 3.0 update notes

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.

既知の問題

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

When you first start Stash after upgrading to Stash 2.9 a repository update task runs that optimizes the pull request refs for all repositories managed by Stash. It's important that you do not interrupt this update process. You can track the progress of this in the Stash logs. See  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 refer to the  Running Bitbucket Server as a Windows service page for 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.

既知の問題