How do I create a regularly reinstalled environment?

[Tim Straub]

Hi,

we would like to use a development system which is copy of the production environment.

To test the system we have to reinstall it all the time.

Now we make a clone of our production system copy it and then we have a lot to do manually.

For every copy we have to change the LDAP connection string, delete private projects, change globe security settings and much more.

Doing all this takes a lot of time.

Is there any possibility to make a development system which is duplicated from our productive system without doing a lot of handwork?

Thank you in advance

Tim

[Thomas Deiler · Accepted solution]

Dear @Tim Straub,

sure you can, this just depends on you technical skills. The changes in the file system (eg. path configurations) could be scripted. The unix patch mechanism is one way of many possible ways.

The other changes need to be done in the database. Solution A: Change everything directly with SQL - but Jira should be down. Solution B would be modified the XML dump and restore the modified one.

So long

Thomas 

[Tim Straub]

@Thomas Deiler,

I've found a lot of settings directly available in the SQL db.

1. So what are the steps to create a test environment with the methods you provide?
2. Set up base system
3. copy / make / change the settings from productive database into the test environment
4. import projects using modified XML dump?

Thank you in advance.

Regards

Tim

[Thomas Deiler]

Dear @Tim Straub,

when I understood you right, you would like to clone prod to test without manual interaction, right?

When the following perquisites are fulfilled:

• Second server with same configuration (RAM/diskspace/JDK/...)
• New DB and its credentials + drivers (JDBC if required)

Then

• write a script that pulls jira binaries + jira_home to server
• and that changes the files server.xml/dbconfig.xml and the $JIRA_HOME path if it is not similar
• write a script that clones the DB (DB to DB) but be aware that this could lead to data nonsense while Jira Prod is running.
• write a script that dose the DB modification to your cloned DB (incl. exchange live license with a developer license)
• start cloned Jira

If you would like to repeat running your scripts, you need to implement some cleaning up before proceeding.

Note: if you drive a VM environment and even the DB is running on that VM, you could just clone a snapshot and only need to run a script, that fixes server.xml/dbconfig.xml and the database settings before switching on.

So long

Thomas

[Tim Straub]

Hi @Thomas Deiler 

thank you I'll give it a try.

Regards,

Tim