Installs/Configures Atlassian JIRA. Please see COMPATIBILITY.md for more information about JIRA releases that are tested and supported by this cookbook and its versions.

• Chef 11+ for version 2.0.0+ of this cookbook

• CentOS 6
• RHEL 6
• Ubuntu 12.04

• Microsoft SQL Server
• MySQL
• Postgres

Required Opscode Cookbooks

• apache2 (if using apache2 recipe)
• ark
• database (if using database recipe)
• mysql (if using database recipe with MySQL)
• postgresql (if using database recipe with Postgres)

Required Third-Party Cookbooks

• mysql_connector (if using MySQL database)

Suggested Opscode Cookbooks

• java
• tomcat

The Atlassian JIRA Linux installer will automatically configure a bundled JRE. If you wish to use your own JDK/JRE, with say the java cookbook, then as of this writing it must be Oracle and version 1.6 (Supported Platforms)

Necessary configuration with java cookbook:

• node['java']['install_flavor'] = "oracle"
• node['java']['oracle']['accept_oracle_download_terms'] = true
• recipe[java]

A /ht to @seekely for the documentation nudge.

These attributes are under the node['jira'] namespace.

These attributes are under the node['jira']['build'] namespace and used to control the JIRA WAR build process.

These attributes are under the node['jira']['container_server'] namespace.

All of these node['jira']['database'] attributes are overridden by jira/jira encrypted data bag (Hosted Chef) or data bag (Chef Solo), if it exists

These attributes are under the node['jira']['jars'] namespace and are for downloading/deploying JIRA JARs in WAR installations.

These attributes are under the node['jira']['jvm'] namespace.

These attributes are under the node['jira']['tomcat'] namespace.

Any node['jira']['tomcat']['key*'] attributes are overridden by jira/jira encrypted data bag (Hosted Chef) or data bag (Chef Solo), if it exists

These attributes are under the node['jira']['war'] namespace and used to control the JIRA WAR deploy process.

• jira_jars: JIRA JARs download/deploy
• jira_war: JIRA WAR download/build

Here's a quick example of downloading and building JIRA WAR:

# Download and build JIRA WAR
jira_war node['jira']['install_path'] do
  action :build
end

See full documentation for each LWRP and action below for more information.

Below are the available actions for the LWRP, default being download.

These attributes are associated with this LWRP action.

Deploy custom list of JIRA JARs to custom location:

jira_jars '/opt/atlassian/jira-jars' do
  deploy_jars %w{carol carol-properties hsqldb jonas_timer jotm jotm-iiops_stubs jotm-jmrp_stubs jta objectweb-datasource ots-jts xapool}
  lib_path '/usr/local/my-special-snowflake-tomcat/lib/'
  action :deploy
end

These attributes are associated with this LWRP action.

Download custom version of JIRA JARs:

jira_jars '/opt/atlassian/jira-jars' do
  version '6.0'
end

Below are the available actions for the LWRP, default being download.

These attributes are associated with this LWRP action.

Run custom ant targets for JIRA WAR build:

jira_war '/opt/atlassian/jira' do
  targets 'generic'
  action :build
end

These attributes are associated with this LWRP action.

Download custom version of JIRA WAR:

jira_war '/opt/atlassian/jira' do
  version '6.1.4'
end

• recipe['jira'] 'Installs/configures Atlassian JIRA'
• recipe['jira::apache2'] 'Installs/configures Apache 2 as proxy (ports 80/443)'
• recipe['jira::build_war'] 'Builds JIRA WAR'
• recipe['jira::container_server_configuration'] 'Configures container server for JIRA deployment'
• recipe['jira::container_server_jars'] 'Deploys database/JIRA jars to container server'
• recipe['jira::database'] 'Installs/configures MySQL/Postgres server, database, and user for JIRA'
• recipe['jira::installer'] 'Installs/configures JIRA via installer'
• recipe['jira::standalone'] 'Installs/configures JIRA via standalone archive'
• recipe['jira::sysv'] 'Installs/configures JIRA SysV init service'
• recipe['jira::war'] 'Installs JIRA WAR'

Optionally for securely overriding attributes on Hosted Chef, create a jira/jira encrypted data bag with the model below. Chef Solo can override the same attributes with a jira/jira unencrypted data bag of the same information.

required:

• ['database']['type'] - "mssql", "mysql", or "postgresql"
• ['database']['host'] - FQDN or "localhost" (localhost automatically installs ['database']['type'] server)
• ['database']['name'] - Name of JIRA database
• ['database']['user'] - JIRA database username
• ['database']['password'] - JIRA database username password

optional:

• ['database']['port'] - Database port, defaults to standard database port for ['database']['type']
• ['tomcat']['keyAlias'] - Tomcat HTTPS Java Keystore keyAlias, defaults to self-signed certifcate
• ['tomcat']['keystoreFile'] - Tomcat HTTPS Java Keystore keystoreFile, defaults to self-signed certificate
• ['tomcat']['keystorePass'] - Tomcat HTTPS Java Keystore keystorePass, defaults to self-signed certificate

Repeat for other Chef environments as necessary. Example:

{
  "id": "jira",
  "development": {
    "database": {
      "type": "postgresql",
      "host": "localhost",
      "name": "jira",
      "user": "jira",
      "password": "jira_db_password",
    },
    "tomcat": {
      "keyAlias": "not_tomcat",
      "keystoreFile": "/etc/pki/java/wildcard_cert.jks",
      "keystorePass": "not_changeit"
    }
  }
}

The simplest method is via the default recipe, which uses node['jira']['install_type'] (defaults to installer).

• Optionally (un)encrypted data bag or set attributes
  • knife data bag create jira
  • knife data bag edit jira jira --secret-file=path/to/secret
• Add recipe[jira] to your node's run list.

Operates similarly to installer installation, however has added benefits of using ark to create version symlinks of each install. Easily can rollback upgrades by changing node['jira']['version'].

• Optionally (un)encrypted data bag or set attributes
  • knife data bag create jira
  • knife data bag edit jira jira --secret-file=path/to/secret
• Set node['jira']['install_type'] to standalone
• Add recipe[jira] to your node's run list.

There are three phases of JIRA WAR support:

• Downloading JIRA WAR archive
• Building JIRA WAR
• Deploying JIRA WAR with necessary JAR dependencies and container server configuration

Each of the phases can be handled separately as outlined below if you need to customize the WAR or deploy it to different nodes than where its being built. By default, cookbook will handle all three phases with node['jira']['install_type'] set to war.

Handled by war recipe using ark so it'll save versioned symlinks. Location customizable by node['jira']['install_path']. From here, the WAR is ready to be customized and built.

Handled by build_war recipe and can be disabled by setting node['jira']['build']['enabled'] to false. Customize build targets via node['jira']['build']['targets']. Expects build output to write file to node['jira']['build']['file'] otherwise will build every convergence. Note node['jira']['build']['exclude_jars'] will by default delete JARs that are recommended to be installed in container server lib directory (node['jira']['lib_dir']) from separate JIRA JARs download.

While cookbook defaults to handling Tomcat build, you may be able to try and deploy the "generic" WAR. Set node['jira']['container_server']['name'] to generic.

There are a couple pieces necessary for successful JIRA WAR deployment:

• WAR file built and ready (node['jira']['war']['file'], which defaults to node['jira']['build']['file'])
• Download and installation of JIRA JARs
• Download and installation of database JARs (such as MySQL Connector/J, etc.)
• Configuration of container server (such as Tomcat)

Atlassian supports deploying WAR only on Tomcat 6/7 and the cookbook handles this case (recommended usage with Opscode Tomcat cookbook), however if you're feeling adventurous, this process may be workable for other container servers with some slight configuration and a wrapper cookbook.

Cookbook handles the above steps with:

• WAR file: built via build_war recipe (using jira_war LWRP) or location up to you with a wrapper cookbook and node['jira']['war']['file'] set appropriately
• JIRA JARs: container_server_jars recipe (using jira_jars LWRP) with configuration in node['jira']['jars'] attributes and node['jira']['install_type'] set to war
• Database JARs: container_server_jars recipe and appropriate database type needing additional JARs
• Configuration of container server: container_server_configuration recipe, which installs context to Tomcat if node['jira']['container_server']['name'] is tomcat.

Using individual recipes, you can use this cookbook to configure JIRA to fit your environment.

• Optionally (un)encrypted data bag or set attributes
  • knife data bag create jira
  • knife data bag edit jira jira --secret-file=path/to/secret
• Add individual recipes to your node's run list.

• Quickly testing with Vagrant: VAGRANT.md
• Full development and testing workflow with Test Kitchen and friends: TESTING.md

For Vagrant, you may need to add the following hosts entries:

• 192.168.50.10 jira-centos-6
• 192.168.50.10 jira-ubuntu-1204
• (etc.)

The running JIRA server is then accessible from the host machine:

CentOS 6 Box:

• Web UI (installer/standalone): https://jira-centos-6/
• Web UI (Tomcat deployed war): http://jira-centos-6:8080/jira/

Ubuntu 12.04 Box:

• Web UI (installer/standalone): https://jira-ubuntu-1204/
• Web UI (Tomcat deployed war): http://jira-ubuntu-1204:8080/jira/

Please see contributing information in: CONTRIBUTING.md

• Brian Flad ([email protected])

Please see licensing information in: LICENSE