Version 6.4.10
A containerized installation of Atlassian JIRA setup with a goal of keeping the installation as default as possible, but with a few Docker related twists.
Want to help out, check out the contribution section.
Here you can read about significant changes to the repository/Docker image.
The Java Runtime Environment has been updated to use OpenJDK 8 and there has been some changes to the installation and home directory to better follow the Filesystem Hierarchy Standard. Thanks @frederickding for noticing and suggesting some changes. The environment variable values has been changed accordingly.
The installation directory /opt/atlassian/jira is not mounted as a volume as standard anymore. Should you need to persist changes in this directory run the container with the additional argument --volume /opt/atlassian/jira.
To quickly get started with running a JIRA instance, first run the following command:
docker run --detach --publish 8080:8080 cptactionhank/atlassian-jira:latestThen use your browser to nagivate to http://[dockerhost]:8080 and finish the configuration.
For a more in-depth documentation on how to get started please visit the website made for this purpose. cptactionhank.github.io/docker-atlassian-jira
This has been made with the best intentions and current knowledge and thus it shouldn't be expected to be flawless. However you can support this repository with best-practices and other additions. Cirlce-CI has been setup to build the Dockerfile and run acceptance tests on the Atlassian JIRA image to ensure it is working.
Circle-CI has been setup to automatically deploy new version branches when successfully building a new version of Atlassian JIRA in the master branch and serves as the base. Futhermore an eap branch has been setup to automatically build and commit updates to ensure the eap branch contains the latest version of Atlassian JIRA Early Access Preview.
Out of date documentation, lack of tests, etc. you can help out by either creating an issue and open a discussion or sending a pull request with modifications to the appropiate branch.
Acceptance tests are performed by Circle-CI with Ruby using the RSpec, Capybara, and phantomjs frameworks.