Last week I presented at the London Atlassian User Group. The title of the presentation was “Deploying Atlassian Tools in the Enterprise”. You can view the slide set here. I tried to keep the presentation on the general side but following on, I thought I would dive a little deeper into the detailed implementation for those who are interested.
I am not going to go over the whole introduction part of the presentation in detail but to quickly review…
- In my experience, the challenge of deploying a large number of application instances drove my teams to look for better ways to manage deployments.
- Its not just about large numbers of instances, it can help any environment with having a controlled way to manage application environments.
- The approach that you take will depend on the environment that you work in. Utilise the infrastructure and knowledge that you have within your team or organisation.
- This process is not just applicable to JIRA or Atlassian tools – it can be used for other application deployments.
For most Atlassian applications, there are two main parts of the deployment – the application (binaries, configuration, etc) and the data (database, attachments, temporary files, etc) . I am not going to go into the data part in detail during this set of posts but focus on the application deployment. For the application deployment, there are three components that we will break down:
- Packaging using the RPM Maven Plugin
- Configuration stored in Subversion
- Deployment Method using Bamboo
So, watch out for Part 2 – I will start on the detail into the Packaging with the RPM Maven Plugin.
the jira guy