I'm using Ansible to create a fully automated instance of JIRA. The main use-case is that it will allow us to test changes, upgrades, etc. on a test instance before we do it in production. I have the install all done as well as the database configuration. Where I'm blocked is the setting of the license. Is there any way to programmatically set this? If not, is there a certain file/folder I could grab from the production instance that would satisfy the licensing requirement? Basically, I want to press a button, go get some coffee, and come back to where I can open up a browser and be ready to create a project. Thanks!
I'm trying the same by Ansible.
Since JIRA 7 the license information is stored in the database table productlicense.
You can automate your configuration by updating this table by inserting the license.
At the moment I am able to updating the application properties (app title and base url) by the table propertystring and the license by updating the table productlicense. I am still looking for a way to automatically create the administration user to avoid the last step in the setup wizard.
Atlassian seems to be using the "unattended installation" verbiage to cover this scenario. I think the best option here is to use the .bin installer and use a varfile as documented here: https://confluence.atlassian.com/adminjiraserver071/unattended-installation-855475683.html
AFAIK you will need a database dump/backup to get the configuration part completed. During the setup wizard as far as I can tell, there is a connector file (dbconfig.xml) created and the database is set up with the proper tables.
Here are a couple of playbooks that will help get people started:
I solved the auto-configuration issue by installing Jira (with a temp license) and taking a backup of the database. On a fresh set of machines, I reinstalled the database + restored the database from the first install, then installed the Jira Software (with the dbconfig.xml).
If you have data in the application (projects etc) you should take a backup of the data and restore that before starting Jira, this will prevent any issues with the database and app data being skewed.
@Ryan Morten, not really. The way I ended up setting it up was my ansible script logs into the production console, grabs the latest backup, and then scp's it to the test instance's /var/atlassian/applicaton-data/jira/import folder. I still have to manually go through 2 screen to select "Restore" and the filename to restore from. If they had a "restore" API, i figured i could get this fully automated.
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event