페이지 트리
메타 데이터의 끝으로 건너뛰기
메타 데이터의 시작으로 이동

한글가이드

  • 아래 가이드는 일반적인 설치환경을 기반으로 하였으므로 설치환경이 특별한 EAR/WAR 배포본 설치의 경우는 영문가이드를 같이 참조하시기 바랍니다.
  • 업그레이드는 반드시 운영서버와 동일한 테스트 환경을 구성하여 업그레이드 테스트를 먼저 수행 하실 것을 권장합니다.
  • 테스트 환경의 서버에서는 반드시 Developer 라이센스 혹은 평가용 테스트 라이센스를 이용하시기 바랍니다.
  • Crowd 를 현재 사용하는 고객의 경우 테스트 서버 구성 하기 전에 반드시 Local 디렉터리에 로컬관리자 계정을 추가하시기 바랍니다. (tick) 로그인 문제 발생 시 로컬관리자 계정으로 로그인하여 처리하기 위함입니다.

업그레이드 할 버전선택

  • 업그레이드 할 버전은 특별히 새로운 기능을 빠르게 사용할 목적이 아니라면 X.X.3 이상의 버전이 릴리스 된 이후 해당 버전으로 업그레이드 할 것을 권장합니다. (예를들어 현재 최신버전이 6.2.x 라면 최소 6.2.3 이상의 패치버전으로 선택)
  • 시스템 안정성을 최우선으로 하는 경우는 현재 릴리스된 최신 버전의 한단계 아래의 Major 버전의 최종 패치버전을 설치하시기를 권장합니다. (예를들면 현재 최신버전이 6.2.x 라면 6.1 의 최종 패치버전 (ex : 6.1.17) 을 선택)


(준비사항)

(1) JIRA가 Crowd 나 LDAP 과 연동된 경우라면 JIRA 자체의 로컬 관리자계정을 추가
(2) Standalone 배포본으로 설치 시 기존서버에 CATALINA_HOME, CATALINA_BASE 과 CATALINA_OPTS 환경변수가 설정되어 있다면 모두 설정해지 (unset)

(3) 현재 서버에 설치 운영되는 JDK, Database 와 사용자가 주로 사용하는 Browser 가 새로운 Confluence 버전이 지원하는 플랫폼 인지 확인 (Supported Platforms 문서 참조)

JDK 및 데이터베이스는 업그레이드 과정 중 에러가 발생하는 경우가 아니면, 업그레이드 완료 후 변경하는 것을 권장합니다

 

(4) 애드온 호환성 체크를 미리 할 수 있는 경우 (Application Manager 버전에 따라 가능하지 않은 경우 있음)  미리 사용하는 플러그인들에 대해 호환성을 체크

(5) 현재 서버에서 사용하는 Database 에 대해 업그레이드 시의 발생 가능한 문제점을 아래 문서 참조하여 확인

https://confluence.atlassian.com/display/CONFKB/Database+Troubleshooting

MySQL 에서의 중요체크사항

--max_allowed_packet=32M 가 설정되어야 하며, InnoDB 엔진을 사용하여야 업그레이드 시 문제가 발생하지 않음. 만약 InnoDB 엔진이 아니라면 MySQL MyISAM을 InnoDB 테이블로 변경하기문서 참조하여 변경해야 함.

(6) Confluence 설치폴더의 파일을 수정해 커스터마이즈한 내용에 대해 별도로 기록하기

(7) JIRA의 사용자정보를 Confluence에서 연동하여 사용중인 경우는 반드시 JIRA 4.3 버전 업그레이드 전에 먼저 Confluence 3.5 로 먼저 업그레이드 해야 함


1. JIRA 이전버전 셧다운 및 JIRA 이전버전의 Home 디렉터리 복사본 및 DB 복사본 생성

 - 가능하면 jiradb43 과 같은 형태로 이름에 버전정보 포함하는 것이 좋 -
 - Home 디렉터리는 atlassian-jira-x.x.x-standalone-home 이나 atlassian-jira-x.x.x-standalone-data 와 같은 이름으로 복사 후 변경
 - (주의사항) Home 디렉터리는 JIRA 설치디렉터리 내부에 위치해서는 안됨


2. JIRA 신규버전 다운로드 및 설치 (압축풀기)

  • 이전 JIRA 버전은 JIRA Archive 사이트에서 다운로드 하실 수 있습니다
  • JIRA 4.4.5 버전의 경우 JDK 1.6 에서 진행하여야 문제가 발생하지 않습니다.
  • 최신버전의 경우 Supported Platforms 에서 사용가능한 JDK 버전을 확인해 진행하시기 바랍니다.

3. JIRA 신규 버전과 (1)에서 복사한 Home 디렉터리 연결하기

 - Home 디렉터리 연결은 (2)의 설치 폴더의 atlassian-jira/WEB-INF/classes 폴더내의 jira-application.properties 파일내의 jira.home 항목값에 복사한 Home 디렉터리의 경로를 지정

4. 데이터베이스 드라이버 확인

 - DB연결 전 데이터베이스(MySQL 등) 드라이버 포함여부 확인하고 없는 경우 다운로드(http://dev.mysql.com/downloads/connector/j)하여 복사 (JIRA 버전에 따라 상이함, 4.3 버전의 경우 포함되어 있음)
 - 데이터베이스 (MySQL 등) 드라이버 복사위치는 <JIRA 설치폴더>/lib (드라이버 파일명은 mysql-connector-java-5.1.x.jar 형태임)

(참조링크) https://confluence.atlassian.com/display/JIRA062/Connecting+JIRA+to+MySQL#ConnectingJIRAtoMySQL-2.CopytheMySQLJDBCdrivertoyourapplicationserver

5. JIRA 신규 버전과 (1)에서 복사한 DB 및 연결하기

 - DB 연결설정은 일반적으로 <JIRA Home디렉터리> 아래에 있는 dbconfig.xml 파일을 수정 (JIRA 이전버전의 파일내용 참조)
   (주의사항) JIRA 5.1 이상 버전부터는 MySQL 사용 시 dbconfig.xml 의 연결 URL 에 sessionVariables=storage_engine=InnoDB (윈도우즈) 혹은 sessionVariables=storage_engine%3DInnoDB (리눅스) 파라미터 추가 필요

 

JIRA 4.3 이하 버전인 경우

  • JIRA 4.3 이하 버전에서는 <JIRA 설치폴더>/conf/server.xml 파일 및 <JIRA 설치폴더>/atlassian-jira/WEB-INF/classes/entityengine.xml 파일수정 (JIRA 이전버전의 파일내용 참조)

JIRA 4.3 버전에서 최신버전 업그레이드 하는 경우 or EAR/WAR 버전을 Standalone 버전으로 변경하는 경우

1. 업그레이드 할 JIRA 버전을 임시로 다른 경로에 신규로 설치합니다.
 - 임시 DB와 임시 Home 디렉터리 생성 후 구동하여 셋업마법사를 이용해 DB 연결하여 신규설치를 진행해 완료합니다.
 - dbconfig.xml 파일을 얻기 위한 목적이므로 해당 파일을 얻고 나면 삭제하시기 바랍니다.

2. (1)에서 생성된 <Home 디렉터리>/dbconfig.xml 파일을 업그레이드 진행 할 JIRA 버전의 Home 디렉터리에 복사 후 편집
 - dbconfig.xml  파일의 DB 연결 URL을 수정합니다.
 - 기존 버전의 연결설정 중 반영할 파라미터가 있는 경우 반영해 줍니다. (tick) JIRA 4.3 버전의 경우는 entityengine.xml 및 server.xml 파일을 참조하여 수정 (매핑방법은 이곳 문서 참조)
  • MySQL JDBC 드라이버의 버전이 낮은 경우는 sessionVariables 파라미터를 지원하지 않을 수 있으므로 에러발생 시는 해당 파라미터를 제공하고 구동하거나 드라이버를 최신버전으로 업그레이드 하시기 바랍니다.

JIRA를 EAR/WAR 버전으로 별도 톰캣에 설치한 경우

  • 만약 JIRA를 EAR/WAR 버전으로 별도 톰캣에 설치한 경우는 <톰캣설치폴더>/conf/Catalina/localhost/jira.xml 파일 및 <톰캣설치폴더>/edit-webapp/WEB-INF/classes/entityengine.xml 파일 수정 (JIRA 이전버전의 파일내용 참조)

 

(참조링크) https://confluence.atlassian.com/display/JIRA043/Connecting+JIRA+to+MySQL#ConnectingJIRAtoMySQL-5.Configurethedatabaseconnectionmanually

6. 기존 JIRA 의 설정내용을 새로운 JIRA 에 적용하기

 - 아래의 파일들을 기존 JIRA 의 설정파일을 참조하여 적용
 - <JIRA설치폴더>/atlassian-jira/WEB-INF/classes/ira-application.properties (EAR/WAR 버전인 경우 webapp/WEB-INF/classes 폴더)
 - <JIRA설치폴더>/bin/setenv.sh (윈도우즈의 경우 setenv.bat) (EAR/WAR 버전인 경우 <톰캣(혹은 다른 어플리케이션) 설치폴더>/bin 폴더)
 - <JIRA설치폴더>/conf/server.xml (EAR/WAR 버전인 경우 <톰캣(혹은 다른 어플리케이션) 설치폴더>/conf 폴더) (tick) 톰캣자체와 연관된 부분은 수정하지 말것
 - Crowd 연동된 경우 <JIRA설치폴더>/atlassian-jira/WEB-INF/seraph-config.xml (EAR/WAR 버전인 경우 webapp/WEB-INF/classes 폴더)

 - Crowd 연동된 경우 <JIRA설치폴더>/atlassian-jira/WEB-INF/classes/crowd.properties (EAR/WAR 버전인 경우 webapp/WEB-INF/classes 폴더)
 - Crowd 혹은 LDAP 연동된 경우 <JIRA설치폴더>/atlassian-jira/WEB-INF/classes/osuser.xml 파일 (파일이 없는 경우 이전 JIRA 버전에서 복사)

(참조) http://confluence.goldpitcher.co.kr/pages/viewpage.action?pageId=85229574 문서의 3-3번 항목

 

7. 기존의 톰캣 캐쉬정보 삭제

 -  <JIRA-Home디렉터리>/plugins/.bundled-plugins
 -  <JIRA-Home디렉터리>/plugins/.osgi-cache
 -  <JIRA-설치폴더>/work/Catalina/localhost

8. 새로운 JIRA 버전 구동

 - 자동으로 업그레이드 진행되고 완료 후 접속가능한 상태가 되면 로그인

9. 업그레이드 이후의 체크사항

 - JIRA 로그 (<JIRA Home 디렉터리>/logs/atlassian-jira.log 파일) 에 중요한 에러메시지 발생 여부 확인

 - 만약 이전에 JIRA External User Management 기능이 ON 으로 설정된 경우 새로운 JIRA 에서도 수동으로 On 설정 해주어야 함 (https://confluence.atlassian.com/display/JIRA062/Configuring+JIRA+Options#ConfiguringJIRAOptions-options)

 - 관리자메뉴에서 인덱스, 첨부, 백업 경로가 제대로 되었는지 및 Base URL 정상적으로 지정되었는지 확인 (tick) 이전 JIRA 버전의 값으로 되어 있는 경우 현재 JIRA 버전에 맞게 수정

 - 메일기능 동작여부 확인 (tick) 경우에 따라 메일서버에서 새로운 JIRA 서버의 연결을 거부하여 메일기능이 동작하지 않는 경우가 있음

 - 기본적인 기능에 대한 검증 (메뉴, 검색, 권한설정, 첨부파일)

 - 사용자 설치 플러그인 동작확인

 - 기존 JIRA 설치 폴더에서 JSP 혹은 VM 파일 등 기타 커스터마이즈 목적으로 수정한 파일이 있는 경우 새로운 JIRA 에서 필요한지 파악 후 필요한 경우 적용 (tick) 새로운 JIRA에서는 적용하였을 때 문제가 발생하는 경우, 다른 방법을 검토해야 함

 - Crowd 와 연결되어 SSO 설정된 경우 SSO 연결테스트

 

영문가이드

If you're upgrading to JIRA 7.0, you should consult the Migration hub. JIRA 7.0 contains functionality that affects your user management, application access and log in permissions, and it's very important that you understand the requirements and the implications before you upgrade. The Migration hub has all this information in one handy space.

 

 

This page describes how to upgrade JIRA installations that don't support the rapid upgrade method or fallback method. You should use this method to upgrade JIRA if you meet any of the following criteria:

  • You use a WAR distribution of JIRA version 4.0.0 or later.
  • You use JIRA 4.0.0 or later on Solaris.
  • You use JIRA 4.0.0 – 4.2.x on Windows or Linux.
  • You use JIRA prior to 4. Note that these versions will require an upgrade to JIRA 4.4.5 before moving on with newer versions.

See Upgrading JIRA for more information on the methods you can use to upgrade JIRA.

(warning) Please read/perform all steps and sub-steps in consecutive order.

1. 시작하기 전에

  1. Read about the new version - Review the release notes and upgrade notes for the version of JIRA that you are upgrading to. See Production Releases. If you plan to skip a few JIRA versions during your upgrade, we strongly recommend that you read the upgrade guides for all major versions between your current version and the version to which you are upgrading. Refer to Important Version-Specific Upgrade Notes for quick links to these guides.
  2. Check your license - Verify that your license support period is still valid. Upgrading to a version prior to JIRA 6.2.4 on an expired license could lead to the error described in After upgrade JIRA shows 500 error page with message User has no unique key mapping.
  3. Check for known issues - Use the JIRA Knowledge Base to search for any issues in the new version that will affect you.
  4. Check for compatibility
    • Confirm that your operating system, database, other applicable platforms and hardware still comply with the requirements for JIRA 6.4. The End of Support Announcements for JIRA page also has important information regarding platform support for future versions of JIRA.
    • If you have installed JIRA plugins (i.e. not included with JIRA), verify that they will be compatible with the version of JIRA you are upgrading to. You can find a plugin's compatibility information using Checking add-on compatibility with application updates or from the plugin's home page on the Atlassian Plugin Exchange.
    • Some anti-virus or other Internet security tools may interfere with the JIRA upgrade process and prevent the process from completing successfully. If you experience or anticipate experiencing such an issue with your anti-virus/Internet security tool, disable this tool before proceeding with the JIRA upgrade.

 

We strongly recommend performing your upgrade in a test environment first. Do not upgrade your production JIRA server until you are satisfied that your test environment upgrade has been successful.

  • If you have any problems with your test environment upgrade which you cannot resolve, create an issue at our support site so that we can assist you.
  • If you have any problems during the upgrade of your production JIRA server, do not allow your users to start using this server. Instead:
    • Continue to use your old JIRA server — this will help ensure that you do not lose production data.
    • Also create an issue at our support site so that we can help you resolve the problems with your upgrade.

2. 백업

Before you begin the JIRA upgrade, we strongly recommend that you back up your existing JIRA installation.

 

2.1 사용자가 JIRA 데이터 업데이트 막기

During the upgrade process, you'll export JIRA's database from your existing JIRA installation (via an XML backup) and then restore this backup into a new JIRA installation. To ensure that the data in the XML backup is consistent with the latest data in the system, you must temporarily restrict access to JIRA so users can't update the data. Refer to the Preventing users from accessing JIRA during backups page for more information.

(warning) Be aware! Inconsistent XML backups cannot be restored!

2.2 데이터베이스 백업

Perform an XML backup of your existing JIRA installation's external database. For large JIRA installations, this process may require several hours to complete.

The 'embedded database' is the HSQLDB database supplied with JIRA for evaluation purposes only. If you accidentally use the HSQLDB database in a production system, perform an XML backup of this database and continue on with this procedure.

2.3 JIRA Home directory 백업

  1. Shut down JIRA.
  2. Locate the JIRA Home directory. You can find information about the location of the directory by navigating to the <jira-application-dir>/WEB-INF/classes/jira-application.properties file in your JIRA Installation Directory. Alternatively, you can open the JIRA Configuration Tool to see the directory that is set as your JIRA Home.
  3. Navigate to the directory specified in the configuration file and create a backup of it in another directory.
  4. (오류) Delete the file <jira-home>/dbconfig.xml as soon as the backup is complete.

2.4 JIRA Home 디렉터리 외부에 첨부 및 인덱스 디렉터리가 있는 경우 별도 백업

If the attachments and index directories are located outside of your JIRA Home Directory, you must back them up separately. These pages describe how to find out where these directories are located in your implementation:

  • Your attachments directory — Refer to Configuring File Attachments page in the documentation for your version of JIRA.
  • Your index directory — Refer to Search Indexing page in the documentation for your version of JIRA.

Also refer to Backing Up Data for more information about backing up attachments in JIRA.

2.5 JIRA 설치 디렉터리 백업

The 'JIRA Installation Directory' is the directory into which the JIRA application files and libraries were extracted when JIRA was installed.

3. 새로운 JIRA 설치 셋업

If you are running a 'mission-critical' JIRA server, we highly recommend performing the remaining steps of this guide in a test environment (e.g. using a separate test JIRA database and a copy of your JIRA Home directory) before performing the upgrade in production.  

 

3.1 JIRA 새로운 버전 설치하기

Download and extract the JIRA distribution you require to a new directory. Do not overwrite your existing JIRA installation. Ensure this has been shut down and install the new JIRA version to a new location.

Follow the installation instructions for either:

(정보) If you are using JIRA WAR, remember to build your new JIRA web application and deploy it to your server. For specific instructions, refer to the JIRA WAR installation page for your application server within the Installing JIRA WAR section.

3.2 새로운 JIRA 를 기존 JIRA의 Home 디렉터리 복사본에 연결하도록 설정하기

 If your new JIRA 6.4 installation is on a new server, copy the backup of your existing JIRA Home Directory from the old server to the new server before proceeding.

To set up a "recommended" (not WAR) distribution:

  1. Open the JIRA Configuration Tool.
  2. Click the JIRA Home tab.
  3. Update the JIRA Home Directory field:
    • If your JIRA 6.4 installation is on a new server, update the JIRA Home Directory field to the path of your copied JIRA Home directory.
    • If your JIRA 6.4 installation is on the same server, update the JIRA Home Directory field to the path of your existing JIRA Home directory.
      (정보) For more information about this directory, see JIRA Home Directory.

To set up a WAR distribution:

  1. Edit the jira-application.properties file located within the <jira-application-dir>/WEB-INF/classes subdirectory of your new JIRA 6.4 Installation Directory JIRA Installation Directory.
  2. Update the jira.home property in this file to the path of the new JIRA Home Directory:
    • If your JIRA 6.4 installation is on a new server, update the jira.home property to the path of your copied JIRA Home directory.
    • If your JIRA 6.4 installation is on the same server, update the jira.home property to the path of your existing JIRA Home directory.
      (정보) For more information about this directory, see JIRA Home Directory.
  3. Remove the '#' at the beginning of the jira.home line (so that JIRA no longer regards this line as a comment).
  4. Save your updated jira-application.properties file.

(tick) You can also set your JIRA Home Directory's location by defining an operating system environment variable JIRA_HOME. This value of this variable takes precedence over the value of the jira.home property in the jira-application.properties file in your JIRA Installation Directory. See Setting your JIRA Home Directory for details.

 

3.3 Connect the new version of JIRA to a new, empty database

Create a new, empty database that your new JIRA installation will use to store its data.

Follow the appropriate 'Connecting JIRA to...' instructions for your database from stage 2, although from stage 4 of that procedure, be aware of the yellow note below:

 

If you are using a database (called jiradb, for example) with your existing JIRA installation and the database for your new JIRA installation is running on the same machine or database server, create your new database with a different name (e.g. something intuitive like jiradb_440 for JIRA 4.4.0). However, ensure the new database has identical access permissions to the old JIRA database. Consult your database administrator if you need assistance with this.

(정보) You do not need to create a new database if you are using the embedded HSQL database.

 

3.4 기존의 JIRA 설정을 새로운 JIRA 설치버전에 적용하기

If you have modified properties in configuration files of your existing JIRA installation, make the same modifications in your new JIRA installation. However, because the properties in the configuration files may have changed between versions, you cannot simply copy the configuration files from your existing installation and replace the equivalent files in the new installation.

For each file you have modified in your existing JIRA installation, you need to manually edit each equivalent file in your new JIRA installation and re-apply your modifications. If a file is not present in your new JIRA installation (for example, osuser.xml in recent JIRA versions), then simply copy that file over to your new JIRA installation.

The table below lists the most commonly modified files and their locations within your JIRA Installation Directory:

File

Location in 'recommended' (formerly 'Standalone') JIRA distributions

Location in JIRA WAR

Description

jira-application.properties

atlassian-jira/WEB-INF/classes

webapp/WEB-INF/classes

Location of the JIRA Home Directory and Advanced JIRA Configuration in JIRA 4.3.x and earlier. 

Any custom property values defined in the jira-application.properties file of your existing JIRA 4.3.x (or earlier) installation must be migrated across to thejira-application.properties file of your new JIRA 6.4 installation before you start your new JIRA installation

Upon starting your new JIRA installation, any custom property values in thejira-application.properties file will automatically be migrated across to either the JIRA database or jira-config.properties file. jira.home is the only property of the jira-application.properties file subsequently used by JIRA.

setenv.bat (Windows) or setenv.sh (Linux)

bin

Application server's bindirectory

Increasing JIRA Memory

osuser.xml
(not required if upgrading from JIRA 4.3.0 or later)

atlassian-jira/WEB-INF/classes

webapp/WEB-INF/classes

Modified if you have integrated LDAP with JIRAintegrated Crowd with JIRA, or if you are using a custom form of external user management or user authentication.

seraph-config.xml

atlassian-jira/WEB-INF/classes

webapp/WEB-INF/classes

Modified if you have integrated Crowd with JIRA.

server.xml

conf

Application server'sconfdirectory

Modified in the following situations:

(tick) The version-specific upgrade notes contain details on properties which may have changed in these commonly modified files.

In addition to the files above, you should also consider and/or perform the following configurations as part of the upgrade process:

  • Using JIRA with Atlassian's Crowd? — If you are using Crowd with JIRA, configure your new JIRA to talk to Crowd as described in Integrating Crowd with JIRA.
  • Allocating additional memory to JIRA — If you had previously allocated additional memory to JIRA, do the same for your new JIRA instance. For more information refer to Increasing JIRA memory.
  • Plugins — For any plugins that you had installed in your old JIRA, download the plugin version for your new version of JIRA from thehttp://plugins.atlassian.com site.
  • Character encoding — Ensure that character encoding (i.e. locale) is the same on the new and old locations. Your new version of JIRA may not function correctly if attachments are moved between two system with incompatible encoding.
  • Customisations — If you had made any customisations (code, templates or configuration files), copy over compatible versions of these changes to the new JIRA. (The developers within your organisation who made the customisations to your old version will need to build and test equivalent changes for the new version, and provide you with the files to copy to your upgraded JIRA installation.)
  • (Optional) Running JIRA on a different port — If your new JIRA is installed on the same machine as your old JIRA, you may wish to make sure it runs on a different port (in case you ever need to restart your old JIRA). See Changing JIRA's TCP Ports for details.

 

3.5 새로운 JIRA 시작하기

 

  1. Verify that your old JIRA installation is shut down — if this JIRA server is still operating, shut it down.
  2. If you installed the JIRA WAR distribution within Tomcatdelete the Tomcat work directory before restarting JIRA. If you do not do this, users may encounter errors when they try to display JIRA pages.
  3. Start up your new version of JIRA. For:
    • 'Recommended' distributions — follow the Starting JIRA instructions.
    • WAR distributions — follow the instructions for starting JIRA for your application server within the Installing JIRA WAR section.
      (정보) During the startup process, your new JIRA installation will create any required database indexes. If you created any custom database indexes, please check them afterwards and remove any that duplicate the indexes added by JIRA.

 

Do not restart your old JIRA installation...

If your new JIRA 6.4 installation is on the same server as your old one, it may still be configured to use the same JIRA Home directory as your new JIRA installation. Running two separate JIRA installations which share a common JIRA Home directory can lead to serious data corruption.

Nevertheless, we recommend that you do not delete any aspect (or backed up component) of your old JIRA installation, until you are satisfied that your upgraded JIRA installation is functioning as expected.

 

3.6 이전의 JIRA 데이터를 새로운 JIRA 로 가져오기

After you have started your new JIRA installation, import the data from your old instance into the new instance. You will need the backup file of data from your old JIRA that you created earlier in these instructions (above).

To import your old JIRA data into your new JIRA:

  1. Log in as a user with the 'JIRA System Administrators' global permission.
  2. Select Administration > System > Import & Export > Restore System (tab) to open the 'Restore JIRA data from Backup' page.
    (tick) Keyboard shortcut'g' + 'g' + type 'rest'
  3. In the File name field, specify the XML backup file you created previously during the export process (above). That zipped file should contain two xml files: activeobjects.xml and entities.xml. Both of these files must be included in the zipped file for the import process to work.
  4. Restore the attachments directory that you backed up previously, into the attachments directory of your new JIRA. (See Restoring Data.)
    (정보) Avoid passing through a proxy when performing an XML restore, especially if your JIRA instance is very large. Using a proxy may cause timeout errors.
  5. Access JIRA via your web browser again and log in using a username from your previous JIRA installation.
  6. Take a quick look around your JIRA site to confirm that your projects and issues are present and everything looks normal. You should see the new JIRA version number in the page footer.

 

4. 업그레이드 이후의 체크사항 및 작업

It is strongly recommended that you perform the following checks and tasks after you have started your new instance of JIRA:

  1. Check your server logs for error messages, even if JIRA appears to be running correctly. If there are any errors there that you cannot resolve, create a support case in https://support.atlassian.com, attach your log file and we will advise you on the errors.
  2. If you were previously using External User Management, enable it in the new JIRA instance.
  3. If you changed machines when upgrading, change the paths to the indexes, attachments and backup directories, from within theAdministration section of JIRA.
  4. Enable email, if you disabled it during testing.
  5. If you migrated any customisations from your old JIRA to the new JIRA, ensure that they are tested thoroughly.
    1. If you had downloaded plugins for the new version of JIRA, install the downloaded JAR file(s) in your new JIRA version and carry out any other required installation for the plugin.
    2. If the plugin has a properties file, apply the same changes to it as you had in the old properties file (don't just copy over the old properties file).

 

Congratulations! You have completed your JIRA migration/upgrade.

참고문서

Disabling Auto-Export
Restoring Data
Upgrading JIRA
Switching Application Servers to Apache Tomcat
Switching Databases

Checking Add-on Compatibility with Application Updates

  • 레이블 없음