Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

fisheye not using the correct config.xml file


I "upgraded" fisheye, but the system does not use the original config.xml file which has all of the license keys, repositories, and DB information.


How do I force it to use this file?

1 answer

Have you set the FISHEYE_INST environment variable? I've set up Crucible under Linux recently, and found that the config.xml file in the Crucible server folder was a complete waste of space, because all configs about web-ports, repos etc. are read from the config.xml in the folder defined by the above mentioned variable.

Maybe the variable was changed during the upgrade?

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events