You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
This is a interesting question:
We have JIRA v7.4 running and when I look in the jira folder it shows jira atlassian-jira-4.4.4-standalone ONLY in the folder. When I look in the /usr/home/ it shows the other developer(who is no longer here) downloaded v7.4. I tried to see if they were linked together with a ls -lrt but only the list showed up. Some how they are synchronized together. Any helpful ideas to see where they are sync together? As I have to do a upgrade to 7.7. Thanks in advance!
Thanks. I did the ps -ef | -I java and it /apps/jira/atlassian-jira-4.4.4-standalone/jre//bin/java -Djava.util.logging.config.file=/apps/jira/atlassian-jira-4.4.4-standalone/conf/ running.
I was told that he just ran the "update version".bin and it automatically upgraded alone with the older version of the Jira. Is this a faster way trick and I didn't know about it? LOL I just run the v7.7.bin and it will automatically upgrade to that version on top of what we currently have. I just don't want go to around changing the environments on the server, I rather leave things as is.
Ok, great start. That means you only have one installation running, and you know where it is.
The /jre/bin is quite telling, as older versions needed a separate installation of Java and it had to be a jdk, not jre.
So, the evidence to me strongly suggests a single 4.4 install that has been upgraded to 7.7.
If it's working ok, there's no need to mess with it, all I'd do is add a "readme-<your organisation>.txt" on the root of the jira install and copy in the home directory (you never know where a new admin might look) and document it in your admin space so you don't forget!