[TASK] OPS-445: Have Jira run in versioned install directories #29
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of the Change
Install Jira into its versioned install directory, in order to be able to have a clean
install directory which contains only the content of the tar-ball and to be able to have versions residing in parallel on the
same system.
Benefits
Before tar-balls were installed into /opt/atlassian/jira.
When doing upgrades, the new tar-ball will be extracted to the same install directory, where files of the old version still are present. It may happen that a new version tar-ball adds a conflicting file to the installationdirectory, which causes that Jira is not starting anymore.
Solution is to have every version reside in its own install directory and have the systemd service unit pointing to the latest installed version.