Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

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
4,456,041
Community Members
 
Community Events
176
Community Groups

Bitbucket upgrade does not migrate the context path from server.xml to bitbucket.properties

I upgraded from bitbucket 4.4.14. to version 5  ( then to version 6 ) . During the version 4.x to 5.x upgrade - the new bitbucket looks for context path in <bitbucket_home>/shared/bitbucket.properties . The earlier version had the context path set-up in <bitbucket-install>/conf/server.xml 

I did a install and spend many hour debugging problem owing to missing context . 

Why doesn't the 5.x installer set the correct context path in bitbucket.properties. It may prompt user asking for context path .

Is this behaviour documented some place ?

Is this a bug ?

 

1 comment

Hi Yogesh,

As stated at https://confluence.atlassian.com/bitbucketserver/migrate-server-xml-customizations-to-bitbucket-properties-897811761.html:

 

Upgrading from any version earlier than Bitbucket Server 4.14 or earlier to Bitbucket Server 5.x or later requires that you manually migrate any changes to the server.xml file to the bitbucket.properties file.

So what you found is the expected behaviour.

Cheers,
Christian

Premier Support Engineer

Atlassian

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events