I am upgrading a Jira data center instance in a test environment to validate upgrade procedure.
The installer notes:
Checking for local modifications.
List of modifications made within Jira directories.
The following provides a list of file modifications within the
atlassian-jira directory.
Modified files:
bin/setenv.sh
Removed files:
(none)
Added files:
...
Under `Added files:` there are a number of files listed. My expectation was that there should be (none) files listed because I thought this meant files that have been modified as part of my local instance.
I would like to have some clarification regarding:
1. Are files added during a Jira upgrade listed under Added files? OR
2. Were any files added before the upgrade (in the instance) listed under Added files.
I am assuming 2. is correct - but I just want to confirm this is the correct interpretation.
Thank you!
This is 2!
Those are the files that the installer detects as "drift" (a difference vs the expected configuration).
Hi @Steve Hayes Welcome to the Atlassian Community
I believe it's part of the good practice to keep Jira versions in their own dedicated folder. So when you update, files are added to the new folder with the correct version number.
The modified files are the configuration files that point to the location of the version that is supposed to be running. These files are shared across these multiple instances of Jira (but only one of them should use it at a time).
Kind regards,
Dick
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.