|
|
@@ -467,34 +467,73 @@ sudo /etc/rc.d/init.d/jira start
|
|
|
|
|
|
A salt state can be used for upgrading. See `msoc-infrastructure/salt/fileroots/jira/README.md`.
|
|
|
|
|
|
+## Prepare
|
|
|
+
|
|
|
+1. Go to jira, click on teh Options->Applications option.
|
|
|
+1. Click on "Plan your upgrade"
|
|
|
+1. Review anything that looks dangerous.
|
|
|
+
|
|
|
## Staging the Update
|
|
|
|
|
|
The state will install the update into a new directory (/opt/atlassian/jira-{version}), but will not stop/start it. You should be able to safely run this at any time (still, follow best practices: make backups first, run salt with `test=true`).
|
|
|
|
|
|
1. Download the latest LTS from [Jira Software](https://www.atlassian.com/software/jira/download-journey). Download in .tar.gz
|
|
|
+ a. upgrade to latest release
|
|
|
+ b. Server
|
|
|
+ c. Latest Release
|
|
|
+ d. tar.gz archive
|
|
|
1. Copy to afsxdr-binaries:
|
|
|
```
|
|
|
-aws --profile mdr-common-services-gov s3 cp atlassian-jira-software-8.13.10.tar.gz s3://afsxdr-binaries/jira/atlassian-jira-software-8.13.10.tar.gz
|
|
|
+aws --profile mdr-common-services-gov s3 cp atlassian-jira-software-8.13.10.tar.gz s3://afsxdr-binaries/jira/
|
|
|
```
|
|
|
-1. update init.sls with the latest version
|
|
|
+1. update `msoc-infrastructure/salt/fileroots/jira/init.sls` with the latest version
|
|
|
1. Optionally, update the `okta_jar` using the same steps as above (download from okta admin, downloads).
|
|
|
-1. Run the state.
|
|
|
+1. Optionally, update the `xmlsec` jar using the same steps as above (download from url in `init.sls`).
|
|
|
+1. Do a PR to develop.
|
|
|
+1. Run the state in test, follow cutover below.
|
|
|
+ `salt jira\* state.sls jira --output-diff test=true` # not useful; will show lots of errors, since it doesn't download the update
|
|
|
+ `salt jira\* state.sls jira --output-diff test=false`
|
|
|
+1. Test in test ( https://jira.xdrtest.accenturefederalcyber.com/ ; Configuration is incomplete -- can't even log in )
|
|
|
+1. PR to master
|
|
|
+1. Apply, cutover, and test in prod
|
|
|
|
|
|
## Cutover
|
|
|
|
|
|
-This file does not change to the new version.
|
|
|
+The salt state does not change to the new version.
|
|
|
|
|
|
To cut over:
|
|
|
|
|
|
-1. Judiciously remove older files in /opt/jira-data/jira/export
|
|
|
+1. Judiciously remove older files in `/opt/jira-data/jira/export`
|
|
|
1. Create backups of jira and jira-data
|
|
|
+```
|
|
|
+cd /opt/
|
|
|
+sudo tar cvzf jira-backup.20220818.tar.gz atlassian jira-data
|
|
|
+```
|
|
|
1. Run `sudo systemctl stop jira`
|
|
|
1. Edit `/etc/init.d/jira`
|
|
|
1. Change the path to the updated jira version
|
|
|
1. `sudo systemctl daemon-reload`
|
|
|
1. Run `sudo systemctl start jira && sudo tail -F /opt/atlassian/jira-VERSION/logs/catalina.out`
|
|
|
+1. If it warns "Upgrade: Custom changes have not been carried over", click 'ignore and continue'. If it returns to teh same screen, stop and start jira. The saltstate carried over these changes.
|
|
|
+```
|
|
|
+sudo systemctl restart jira && sudo tail -F /opt/atlassian/jira-9.1.0/logs/catalina.out
|
|
|
+```
|
|
|
+1. Test jira may redirect you to prod jira. Watch your URL!
|
|
|
+
|
|
|
+## Cleanup
|
|
|
+
|
|
|
+Once everything is runnign, there are a few things left:
|
|
|
+1. Clean out hte old directory to remove any warnings.
|
|
|
+```
|
|
|
+cd /opt/atlassian
|
|
|
+rm -rf jira-9.0.0 # or whatever previous version was
|
|
|
+```
|
|
|
+1. Go to the web interface, to the gear (settings)->manage apps
|
|
|
+1. click on 'manage applications' from the new menu
|
|
|
+1. click on 'update' on each application that has an update
|
|
|
+
|
|
|
|
|
|
-You may have to restart jira a second time if it warns about files that weren't updated (they really were!).
|
|
|
+...
|
|
|
|
|
|
## Java Updates
|
|
|
|
Fred Damstra [afs macbook]