nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to setup a JIRA test server

Ryan Grimard

I'm using JIRA standalone. Backend is on SQL Server. I would like to configure a test server, which will allow me to test new workflow changes, plugins, JIRA updates, etc.

What is the best way to configure such a test server? I'm thinking a VM where I can snapshot my "current configuration", then make changes and revert back to the snapshot if necessary.

What is the best way to make the test server match the production server's configuration? Is it as simple as exporting production JIRA configuration and/or projects and then importing into the test server? Or should I clone the production server (physical to VM) and then change the database connection?

Accepted answers

Bob Swift

I would recommend you create and follow a procedure that you would follow in case of a server failure. That means automate your nightly backup procedures, make sure data is off system, and then have a restore plan to get it running on another server (your test server). So not only do you have your test environment set up, but you get confidence in your backup procedures.

All comments

Jo-Anne MacLeod

One way would be to set up the test env, import a xml backup of your production server, copy over your attachments. Then repeat the steps on a nightly bases (I would look at writing a script).

Ryan Grimard

So I would need to install JIRA from scratch, drop in and configure all the plugins I'm using, and then import xml the backup?

What about the backend? On my test server, should I just use the default backend?

Does the XML backup backup the actual issues, or just configuration?

Bob Swift

Yes, issues and configuration. Attachments must be handled separately as mentioned by Jo-Anne.

Bob Swift

Ryan Grimard

This worked great. Just exported a backup from production, imported into test. Then copied over my plugins and attachments. Restart. Done.

Thanks

Ryan

Justin Rand

Following this advice, I'd look to move away from the XML backups and use the native DB backup procedure. You may also want to do this on a VM and (if you have the application available) create a snapshot of your "Production Mirror". That way if any issues arise in your production instance you can easily revert to the mirror and began testing/debugging with little to no effort.

Ryan Grimard

I like that. However, what is the easiest way to configure the JIRA instance to point to the correct db? I had the JIRA install create the DB for me, so I haven't had to repoint one manually yet.

Justin Rand

Should be in your <install-directory>/conf/server.xml file below the HTTPS section. It makes it easy if you have the DB running on the same server. This way you can point it to localhost:<port> and never have to worry about your test instance reaching out to your production DB no matter how many times you copy over your JIRA files.

There is also documentation for setting up DB connections here: http://confluence.atlassian.com/display/JIRA/Connecting+JIRA+to+a+Database