What should we test after migrating JIRA from Windows to Linux?

[Evelin]

We moved JIRA to another server which is a Linux server. What should we test after the migration (aside from the tasks mentioned in Post migration checks section of this page https://confluence.atlassian.com/jira/migrating-jira-to-another-server-151126305.html)?

Are there special Windows to Linux checks?

[rrudnicki · Accepted solution]

Hi Evelin, 

Basically, the most difference from Linux to Windows would be the paths since on Linux as you know, we have directories on /etc, /bin, etc, while on Windows we have C:\, D:\, etc... 

Also, check if there's a firewall enable which can cause some unexpected behaviour. You can check this with "ps -aux" command, "iptables -nL" command, etc.

Don't forget to check the hostname, IP Address, especially if you are authenticating your users against a LDAP/AD server. The same advice to address of your email server. Some network admins have restrict rules between the communication with other machines. 

In case your application doesn't start or have an odd behaviour, check the folder owner/permissions with the command "ls -l". You can change that with chown (owner) or chmod (read/write/execute permissions). 

Keep in mind, we are discussing only a migration to another server and I not covering possible issues related to an UPGRADE, which you should test additional things, like java version, java parameters (specially if you moved to java 8), plugins version/deprecated, etc. 

Lastly, don't forget that the logs are your friend and we also are . Feel free to add logs/questions here or raise a ticket with Atlassian. 

Have a great day, 

Renato Rudnicki

[Evelin]

Renato, thank you very much for your answer! We will check all that. Cheers, Evelin