Skip to content

Latest commit

 

History

History
48 lines (31 loc) · 4.54 KB

README.md

File metadata and controls

48 lines (31 loc) · 4.54 KB
Raw

CircleCI Build Status Open Issues Stars on GitHub Forks on GitHub Stars on Docker Hub Pulls on Docker Hub Sponsor by PayPal

HEADS UP! The latest tag and versions above 3.10.1 will be switching to use Alpine versions of OpenJDK as the base image.

Atlassian JIRA Service Desk in a Docker container

This is a containerized installation of Atlassian JIRA Service Desk with Docker, and it's a match made in heaven for us all to enjoy. The aim of this image is to keep the installation as straight forward as possible, but with a few Docker related twists. You can get started by clicking the appropriate link below and reading the documentation.

If you want to help out, you can check out the contribution section further down.

I'm in the fast lane! Get me started

To quickly get started running a JIRA Service Desk instance, use the following command:

docker run --detach --publish 8080:8080 cptactionhank/atlassian-jira-service-desk:latest

Then simply navigate your preferred browser to http://[dockerhost]:8080 and finish the configuration.

Configuration

You can configure a small set of things by supplying the following environment variables

Environment Variable Description
X_PROXY_NAME Sets the Tomcat Connectors ProxyName attribute
X_PROXY_PORT Sets the Tomcat Connectors ProxyPort attribute
X_PROXY_SCHEME If set to https the Tomcat Connectors secure=true and redirectPort equal to X_PROXY_PORT
X_PATH Sets the Tomcat connectors path attribute

Contributions

This image has been created with the best intentions and an expert understanding of docker, but it should not be expected to be flawless. Should you be in the position to do so, I request that you help support this repository with best-practices and other additions.

Travis CI and CircleCI has been configured to build the Dockerfile and run acceptance tests on the Atlassian JIRA Service Desk image to ensure it is working.

Travis CI has additionally been configured to automatically deploy new version branches when successfully building a new version of Atlassian JIRA Service Desk in the master branch and serves as the base. Furthermore an eap branch has been setup to automatically build and commit updates to ensure this branch contains the latest version of Atlassian JIRA Service Desk Early Access Preview.

If you see out of date documentation, lack of tests, etc., you can help out by either

  • creating an issue and opening a discussion, or
  • sending a pull request with modifications (remember to read contributing guide before.)

Continuous Integration and Continuous Delivery is made possible with the great services from GitHub, Travis CI, and CircleCI written in Ruby, using RSpec, Capybara, and PhantomJS frameworks.