-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
None
-
Affects Version/s: 4.4.3, 6.4.1
-
Component/s: Installation
-
Environment:
redhat, mysql
-
4.04
-
11
-
Severity 3 - Minor
-
2
Steps to reproduce
- download and extract JIRA Zip Archive (not the latest version)
- edit JIRA_Install/bin/setenv.bat and add this parameter to specify JIRA_Home (Windows environment):
- set JIRA_HOME=path/to/jira/home
- start JIRA and set it up, then shut it down
- download JIRA Installer of the latest version and run it to upgrade JIRA
Expected behavior
The installer recognizes JIRA_Home set in setenv.bat
Actual behavior
The following error is thrown:
![]()
Workaround
- quit the Installer
- set jira.home from jira-application.properties or use JIRA Configuration Tool
- run the Installer to upgrade JIRA again
Original Description
Check following transcript - doing a ./atlassian-jira-4.4.3-x32.bin
Create a new JIRA installation. [1, Enter], Upgrade an existing JIRA installation. [2] 2 Existing JIRA installation directory: [/opt/JIRA] /opt/atlassian/jira/install Unable to determine location of the home directory. 'jira.home' was not found inside jira-application.properties. Finishing installation ... [root@testjira download]# grep jira.home /opt/atlassian/jira/install/atlassian-jira/WEB-INF/classes/jira-application.properties # The jira.home property must be set before you start JIRA. It specifies the directory in which JIRA will store its data files. # NOTE: If you are using Windows, you will need to use double \ characters, for example c:\jira\home should be written # You can also use Unix-like paths which Java/JIRA can handle, eg c:/jira/home jira.home = [root@testjira download]# grep -i jira.home /opt/atlassian/jira/install/bin/setenv.sh # One way to set the JIRA HOME path is here via this variable. Simply uncomment it and set a valid path like /jira/home. You can of course set it outside in the command terminal. That will also work. JIRA_HOME="/opt/atlassian/jira/data"Workaround - set the jira.home in jira-application.properties, don't use the one in setenv.sh ...