update forum discourse version from 2.4.0beta5 to 2.4.0beta6
C4
Production Change - Criticality 4Change Objective | update forum discourse version from 2.4.0beta5 to 2.4.0beta6 |
---|---|
Change Type | Update (fixing 3 security issues) |
Services Impacted | forum.gitlab.com |
Change Team Members | Name of the engineers involved in the changehphilipps |
Change Severity | C4 |
Change Reviewer or tested in staging | A colleague will review the change. |
Dry-run output | If the change is done through a script, it is mandatory to have a dry-run capability in the script, run the change in dry-run mode and output the result |
Due Date | 10/21 15:00 UTC |
Time tracking | Update expected to finish within 5m |
Detailed steps for the change. For each step the following must be considered:
- pre-conditions for execution of the step - how to verify it is safe to proceed
- https://forum.gitlab.com/admin/upgrade#/ shows discourse more than 200 commits behind 2.4.0beta6
- execution commands for the step - what to do
- click "Upgrade All" in Admin UI
- post-execution validation for the step - how to verify the step succeeded
- https://forum.gitlab.com/admin/upgrade#/ shows discourse up-to-date
The pingdom alert for forum might be triggered during the update, but usually is not, as the downtime is very brief.
Rollback steps
- checkout the previous version and rebuild the app
./launcher enter app git checkout 302e8f43936b39a09a64935b15b263775544e9b9 exit ./launcher rebuild app
Edited by Henri Philipps