Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

yogesh_devi
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 24, 2019

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 ?

 

2 answers

0 votes
Samatar geedi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 6, 2023

Ok

0 votes
Christian Glockner
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
April 25, 2019

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events