Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Products
See all
Community resources
Interests
See all
Community resources
Top groups
Explore all groups
Community resources
Celebration

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Join now to unlock these features and more

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.

Get started Tell me more
Atlassian Community about banner
4,463,400
Community Members
 
Community Events
176
Community Groups

fisheye not using the correct config.xml file

Edited
Ronson LeVau
Ronson LeVau Jan 31, 2020

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?

Answer
Watch
Like Be the first to like this
330 views

1 answer

0 votes
Snorre Selmer
Snorre Selmer Mar 03, 2020

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?

Reply

Suggest an answer

Log in or Sign up to answer
Fisheye
Fisheye/Crucible
TAGS

Atlassian Community Events

See all events