Purpose

Bitbucket is a comprehensive Git-based Version Control System (VCS). It especially provides repository browsing, pull requests, branch permissions and code-aware searching.

Properties

Topology

The stack consists of two containers:

• vcs-bitbucket: the application container
• vcs-bitbucket-postgresql: the database container

Configuration

There are no stack-specific configuration variables.

See also the variables which control integration of the stack into the reverse proxy.
For changes to take effect the stack has to be reinstalled.

First Steps

Completing the setup

When you first connect to Confluence the setup process will continue.

Confluence will show a Licenses and settings panel, where you choose your application title and the base URL (which should already be filled correctly). You then have to supply a license generated from the displayed Server ID.

In the next panel you define the administrative account, hereafter you are forwarded to the login screen and log in with this account.

Using Bitbucket

At the heart of Bitbucket are the Git repositories. They are grouped into projects, so the first step is usually to creat e one by clicking on the Projects link in the top row. For now it is sufficient to just enter the project's name.

Bitbucket then suggests to create (or import) one or more repositories assigned to this project. You have to give a name to the repository and may choose another default branch than the usual "master".

You are now dropped into a page telling a few ways how to populate your repository. In the example commands you find the HTTP(S)-URL you use to connect to this repository in Git commands. You may either populate the repository with already existing stuff or clone the empty repository to start working on it.

Here are some important UI elements:

• The Repositories link in the top row allows you to chosse between all repositories this user has access to. Bitbucket distinguishes between public repositories which are visible to everyone and private ones with a closed member group.
• The cog wheel in the sidebar to the left leads to the settings of the repository. Here you can configure such details as repository permissions, branch protection, hooks and SSH access keys for interfaces to other tools and how you want to doeal with pull requests.
• The user menu to the very top right lets you manage your account. This includes creating perseonal access tokens for passwordless access over HTTPS to repositories and the Bitbucket REST API.
• The "page" icon next to it offers quick access to your yet unapproved pull requests.
• The search bar targets for commit meassages, code sequences, repository names and more.

When in a repository the left sidebar contains icons for often used operations (use Expand sidebar at the bottom left to also display operation names). They should be familiar for those already knowledgeable in Git.

Throughout Bitbucket you find links to Atlassian's good documentation on Git.

Note that for another Git (Git bash, IDE Git clients etc.) Bitbucket presents itself as a commonplace Git implementations offering all interactions Git offers. The additional value is in the Web UI, permissions, pull requests and branch protection, the REST API and the optional integration with Jira and Confluence.

Technical details on the vcs-bitbucket container

Ports:

• 7990/tcp HTTP Server
• 7999/tcp SSH server
• 5701 tcp/udp Hazelcast port (node-to-node cluster communication)
• 7992/tcp Elasticsearch HTTP interface port (bitbucket to Elasticsearch search requests, on loopback interface only)
• 7993/tcp Elasticsearch transport/node communication port (node-to-node cluster communication, on loopback interface only)

Config File: /data/bitbucket/shared/bitbucket.properties

Elasticsearch Config Files

• elasticsearch.yml
• jvm.options
• log4j2.properties

Related Documents

• Most recent changes