Code search is an integrated feature with Bitbucket Server 4.6.0.
For a normal instance, Elasticsearch is automatically installed and runs alongside your Bitbucket server to index changes to your code. So it should just work out of the box. For Data Center we require you to set up your own ES instance and configure Bitbucket so that it knows where to send code changes.
For more information on how code search works in Bitbucket Server, see https://confluence.atlassian.com/display/BitbucketServer/Search+for+code+in+Bitbucket+Server
@Neil O'Neill The bundled Elasticsearch should come up on port 7992 regardless of installation method. Try the installer if you can, otherwise submit a support ticket at support.atlassian.com with the steps for how you attempted to set up the tarball, and we can look into it in more detail.
@Kristy Hughes - I am running Bitbucket on a linux server and before I proceed with upgrade from 4.3.2 to 4.6.0, would like to know what does below NOTE means. I read this at https://confluence.atlassian.com/bitbucketserver/bitbucket-server-4-6-release-notes-827109988.html
Important note for Data Center users
Bitbucket Data Center 4.6+ does not use the bundled Elasticsearch instance. Instead, you must provision an Elasticsearch instance separately when installing Bitbucket Data Center 4.6+.
Hi @Akul Bhatnagar,
For non Data Center users, we provision and start an Elasticsearch instance with the installer. Bitbucket needs a single URL for Elasticsearch - and for the case of non Data Center users the obvious choice is to install Elasticsearch alongside Bitbucket Server and point the url to localhost.
For Data Center customers, Bitbucket Server is installed on two nodes, and lies behind a load balancer so that it can be accessed from a single url. If we installed Elasticsearch with the installer for Data Center customers, they would end with two Elasticsearch instances on the same instance that their Bitbucket is installed. Since Bitbucket requires a single URL to access Elasticsearch, this wouldn't work. Since Datacenter customers' instances vary widely, we decided that it was best for them to provision their own Elasticsearch instance, instead of using the one that comes with the installer. When you run the installer, if you select that you are installing or upgrading a Datacenter instance, we do not install Elasticsearch but instead assume that you have already set up an Elasticsearch instance.
For more information on how to set up Elasticsearch for Datacenter, see https://confluence.atlassian.com/bitbucketserver/install-and-configure-a-remote-elasticsearch-instance-815577748.html
Hi Bitbucket users,
We are running our Stash DC instance on 3.11.2 and planning to upgrade to Bitbucket 4.7.1 which has inbuilt elastic search functionality.
Do we need to elastic search on same nodes of Bitbucket DC have or it should be on remote instance other than Bitbucket DC
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs