Skip to content

dsf openshift services bitbucket extra server configuration

Jump to bottom
travis edited this page Jul 15, 2019 · 3 revisions

[Under construction]

The purpose of the present document is to provide the basic steps carried out to improve the configuration of BitBucket server in OpenShift.

The improved configuration consists on:

  • Persistent Volume Claims

  • Health Checks (pending to be completed)

Persistent Volume Claims.

Please notice that the BitBucket server container does not use persistent volume claims by default, which means that the data (e.g.: BitBucket server config.) will be lost from one deployment to another.

pvc0

It is very important to create a persistent volume claim in order to prevent the mentioned loss of data.

Step 1: Add storage

pvc1

Step 2: Select the appropriate storage, or create it from scratch if necessary

pvc2

Step 3: Introduce the required information

  • Path as it is specified in the BitBucket server Docker image (/var/atlassian/application-data/bitbucket)

  • Volume name with a unique name to clearly identify the volume

pvc3

The change will be inmediately applied

done

Creative Commons License Agreement
This documentation is licensed under the Creative Commons License (Attribution-NoDerivatives 4.0 International).

devonfw Shop Floor Guide

Provisioning environments

Configuration and services integration

Create project

Deployment environments

Monitoring

Clone this wiki locally