In the devops age of automation the ability to auto install / auto upgrade is key. Confluence and Jira offer a response file for this purpose. But I recently noticed that more often than not these response files do not work correctly.
Two noteworthy examples are executeLauncherAction$Boolean and backupJira$Boolean
We like to use systemd service. Unfortunately executeLauncherAction$Boolean does not seem to work. So on upgrade Jira and Confluence will ignore this setting and launch. Subsequently our systemd tries to start and fails because there is an unexpected Jira instance running. So an automated upgrade will default fail. Extra tinkering / hacking is necessary to get this to work properly.
Another example is backupJira$Boolean. Jira and Confluence will also ignore this setting and perform a backup. When a lot of data is involved this is a showstopper on automating upgrade successfully.
There are tickets for at least some of this issues. My impression is that Atlassian considers the fact that unattended install is not working very well for two important products unimportant. A curious position to have in the devops / automation age.
If you think that automation of upgrades is important, please consider voting for this issues like
This might help trigger an overhaul of the unattended install / upgrade feature and fix the issues and improve documentation.
Or don't use the bin/exe file, just use the tar.gz file and manually add them to the directories you want them to be in.
In that way, you have more freedom on how the settings will be and set up your own service script and the user that controls it.
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