Jira 用にテスト環境を作成する

When you upgrade Jira, we strongly recommend performing the upgrade in a test environment before upgrading your production site.

Replicate your environment

Your test environment should replicate your real-live environment (production), including any reverse proxies, SSL configuration, or load balancer (for Data Center). You can decide to use a different physical server or a virtualized solution but make sure it is an appropriate replica of your production environment. 

For the purposes of these instructions, we assume your test environment is physically separate from your production environment, and has the same operating system (and Java version if you've installed Jira manually). 



1. データベースの複製


  1. 本番環境データベースをバックアップします。バックアップの最良の方法の詳細については、データベースのドキュメントを参照してください。 
  2. Install your database on the test server and restore the backup. 

データベース バックアップのリストア手順は、選択したデータベースとバックアップ ツールによって異なります。以下を確認してください。

  • Your new test database has a different name from your production database.
  • Your test database user account has the same username and password as your production database user account.
  • 文字エンコードおよびその他の設定は本番データベースと同じです (たとえば、Oracle データベースの場合、文字エンコードは Unicode UTF-8 (または AL32UTF8 のはずです)。


2. Jira の複製

To replicate Jira, make a copy of your Jira installation and point it to your test database.

  1. Copy your entire production installation directory to your test server. 
  2. Copy your entire production home directory to your test server. 
  3. Edit <installation-directory>/atlassian-jira/WEB-INF/classes/jira-application.properties to point to your test home directory. 
    DATA CENTER For DC, make this change on every node.
  4. Edit <home-directory>/dbconfig.xml or  <installation-directory>/server.xml (older versions) to point to your test database. 

    Make sure your test environment is not pointing to your production database.


3. Manage shared home directory

  1. Copy the production shared home directory to the test server. 
  2. Edit <local-home-directory>/cluster.properties to point to your test shared home directory. Make this change on every test node. 


4. Start Jira in test environment

  1. Start Jira with the following System Properties to make sure your test site does not send or receive notifications and emails. For more info about disabling email, see Disable email sending/receiving.   


    DATA CENTER Start one node at a time.

    テスト メール通知が必要な場合
  2. Head to  http://localhost:<portand log in to Jira on your test server. 
  3. Go to  > System > General Configuration , and change the base URL of your test site (for example  mysite.test.com ).
  4. > [アプリケーション] > [バージョンとライセンス] に移動し、開発ライセンスを適用します。ライセンスを更新するには、横にある編集アイコンをクリックします。
  5. Go to  > System > System info, and check that Jira is correctly pointing to your test database, and test home directory. 

  6. Go to  > System > Look and feel, and change the colors of the test instance to make it different from the production instance. That's a small change, but it might help you avoid big mistakes.


5. (オプション) 外部ユーザー管理の複製

Crowd または外部 LDAP ディレクトリでユーザーを管理している場合、以下が可能です。

  • replicate Crowd or your external directory in your test environment and point your Jira test site to your test external directory (recommended).
  • provide your test server with network or local access to the same hosts as your production server. 

If you have application links between Jira and other Atlassian applications, you should change the server ID on each test application. See How to change the server ID of Confluence and Changing Server ID for Test Installations for Jira. 

If you don't change the server ID and update your application links there is a chance that when you create a new application link in production it will point to your test server instead.


Head back to the landing page, and complete the pre-upgrade steps.

ランディング ページに移動

最終更新日 2019 年 3 月 26 日


Powered by Confluence and Scroll Viewport.