Details
-
Type:
Task
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Labels:None
-
Story Points:3.5
-
Epic Link:
-
Sprint:Summer 2: 22 Jun - 3 Jul, Summer 3: 6 Jul - 17 Jul, Summer 4: 14 Jul - 28 Jul, Summer 5: 3 Aug - 14 Aug, Summer 6: 17 Aug - 28 Aug, Summer 7: 31 Aug - 11 Sep, Fall 1: 14 Sep - 25 Sep, Fall 2: 28 Sep - 9 Oct
Description
For this task, clone our Jira onto a new VM using the backups or other method as appropriate.
Take very careful notes to ensure that you (or someone else) can easily make a new clone in a short period of time.
Also, develop testing instructions needed to validate that the clone is correct.
Once you have learned all the tricks, make another clone! And then another one
Goal: Decrease the time to create and deploy and test a clone to 1 hour or less.
Attachments
Issue Links
Activity
Created folder in Google Drive containing:
- mysql dump of Jira database from 6/23/20
- jira home directory "tarball" from 6/23/20
- saved Jira system information page (logged in as "admin" user)
Also, see:
Suggested protocol:
- Use ansible playbooks to install dependencies (MySQL, Java, Tomcat)
- Use ansible playbook (if possible) to install Jira version 6.4.8
- Use ansible playbook to modify Apache configuration files to run Jira via a reverse proxy
First drafts are done and are being tested and improved. Moving to Done.