atlassian toolchain

Atlassian Software Suite on AppAgile

This repository contains Docker images including assets and OpenShift templates for eight Atlassian products: – BambooBitbucketConfluenceCrowdCrucibleFishEyeJira CoreJira Software

All of these are based on an Atlassian Base image which in turn is based on Red Hat Enterprise Linux.

Known Issues

OpenJDK

These images contain OpenJDK for licensing reasons that forbid the use of Oracle JDK. However, OpenJDK is not officially supported by Atlassian with their products. See: https://jira.atlassian.com/browse/CONF-16431

Note: In the example of Confluence, Atlassian has chosen OpenJDK themselves for a Docker-based solution.

Base URL Health Check

To ensure full functionality and avoid warnings, it is required for most Atlassian applications that the respective instances can access themselves via the provided base URL, i.e. route URL. Depending on the OpenShift environment, this might require some manual configuration to allow proper domain name resolution in the pods. An easy way of testing this would be: $ oc rsh <Atlassian Pod> $ curl -v <Base URL specified during setup> This issue has so far occurred in the vCloud.

Scaling

Since the home/data directories of the applications in all images in this repository are set to a mounted volume, every started instance of the same deployment will try to access the same files. However, almost all these applications lock their home/data directory after starting. Therefore, it is not possible to start more than one functioning instance at a time with this configuration. The images are hence tagged as “non-scalable”. For the same reason, the recommended pod update strategy is “Recreate” and was also used in the respective templates.

Linking of applications

When attempting to link different Atlassian applications with each other, it is important to ensure the correct URLs are being exchanged. An application (e.g. Crucible) might assume its own URL as e.g. http://HOSTNAME:8060 and provide this to the other one (e.g. Jira) as its access URL. This is incorrect and needs to be amended via advanced settings during the application linking. The proper URL is either the route URL or the service name with port.