Skip to content
Docker container to run JIRA
Shell Dockerfile Makefile
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.

JIRA Container for

Build Status

This container defines JIRA behind The container consists of three main pieces:

  • /srv/jira/base: Upstream JIRA image. Ideally we don't want to touch this at all, unless we absolutely have to.
  • /srv/jira/site: Container local customizations to JIRA image. This also acts as $CATALINA_BASE
  • /srv/jira/home: Persisted portion of the JIRA data, such as attachments

The site portion includes our site-local customizations to JIRA, such as:

  • Adjustment to JVM memory size
  • Different templates for email notifications
  • Customized Tomcat configurations

How to develop this container

You can start this container with mock LDAP and DB.

At the beginning of the development session, you do the following:

  • make startldap to start a mock LDAP container in the background
  • make startdb to start local mariadb container in the background.

At this point, if you have access to the backup of JIRA database and home, do the following optional steps. Note that the backup database contains sensitive information, such as the password to access production LDAP, security vulnerabilities, and so on. So it shouldn't be passed around casually:

  • retrieve database dump as backup.db.gz
  • make restoredb to fill DB with a copy of production data
  • retrieve JIRA_HOME dump as backup.fs.gz
  • make restorefs to fill ./data with a copy of production data

If you omit the above steps, the JIRA container will start empty.

Finally, run make run to build and start JIRA container in the foreground.

When its initialization sequence is all done, point the browser to http://localhost:8080/.

Two valid users exist in mock LDAP container. 'kohsuke' and 'alice'. 'kohsuke' is a super user, 'alice' is a regular user. Password is both 'password'

To make changes to the JIRA container, press Ctrl+C to kill JIRA container, make edits, and run make run again.

Getting database & JIRA Home dumps

Here is the script I use to get the necessary dump out of JIRA:

ssh "mysqldump hudson_jira | gzip" > backup.db.gz

mkdir copy || true
pushd copy
  rsync -avz --exclude=export '--exclude=*.log' --exclude=caches --exclude=index --exclude=log --exclude=tmp .
  tar cvzf ../backup.fs.gz .


  • Javamelody integration (?) mainly in dbconfig.xml
  • oom_adj
You can’t perform that action at this time.