How do you use Bitbucket's code search and navigate large codebases efficiently?

Think of code search like a library's catalog system. A small library (single repository) can get by with a simple card catalog (basic search). But a university library system with thousands of books across multiple buildings (workspace with hundreds of repositories) needs a computerized search system that can find a specific passage across any book in any building. Bitbucket offers both levels, but the capabilities differ significantly between Cloud and Data Center.

Bitbucket Cloud provides code search within individual repositories through the repository's Source view. You can search for filenames, code patterns, and exact string matches. The search supports basic operators like AND, OR, and phrase matching with quotes. Results show file paths and line numbers with context snippets. For workspace-wide search across multiple repositories, Bitbucket Cloud offers a search API at /2.0/workspaces/{workspace}/search/code that accepts a query and returns matches across all accessible repositories. The search index covers the default branch of each repository and is updated as code changes.

Bitbucket Data Center integrates with Elasticsearch for code search capabilities. Administrators configure an Elasticsearch cluster, and Bitbucket indexes all repository content, including commit messages, file contents, and branch names. Data Center's search is more powerful than Cloud's, supporting regex patterns, language-specific syntax highlighting in results, and cross-repository search from the UI. The Elasticsearch integration requires careful capacity planning: indexing hundreds of repositories with millions of lines of code demands significant memory and disk resources on the Elasticsearch nodes.

In production, teams extend Bitbucket's built-in search with several strategies. Developers configure their IDEs (VS Code, IntelliJ) with the Bitbucket plugin to search directly from the editor. Teams with many repositories create a search aggregation script that uses the API to search across all repos and present unified results. Some organizations deploy code search tools like Sourcegraph or OpenGrok alongside Bitbucket for advanced features like symbol navigation, cross-repository references, and dependency graph visualization. These tools index all repositories via Bitbucket API and provide a more powerful search experience than the built-in feature.

A gotcha that frustrates developers: Bitbucket Cloud's search only indexes the default branch. Code on feature branches or in pull requests is not searchable through the workspace search API. If you are looking for code that was recently pushed to a feature branch, you will not find it through search; you need to navigate to the branch directly. Data Center's search can be configured to index additional branches, but this increases index size and rebuild time. Another limitation is that Bitbucket does not support structural code search (e.g., 'find all functions that accept a Config parameter'), which is where tools like Sourcegraph add value.