From cfab2346cf075d4c470f52761f6f6066a34e5ea6 Mon Sep 17 00:00:00 2001 From: Quentin Date: Sun, 22 Nov 2020 13:01:05 +0100 Subject: [PATCH] Another another try --- op_guide/update_matrix.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/op_guide/update_matrix.md b/op_guide/update_matrix.md index 27c12e0..16f6b33 100644 --- a/op_guide/update_matrix.md +++ b/op_guide/update_matrix.md @@ -80,8 +80,8 @@ If everythings worked as intended, you can commit and push your deployment file. If something went wrong, you must rollback your deployment. - 1. First, find a working deployment with [nomad job history](https://www.nomadproject.io/docs/commands/job/history) - 2. Revert to this deployment with [nomad job revert](https://www.nomadproject.io/docs/commands/job/revert) + 1. First, find a working deployment with [nomad job history](https://www.nomadproject.io/docs/commands/job/history) + 2. Revert to this deployment with [nomad job revert](https://www.nomadproject.io/docs/commands/job/revert) Now, if the deployment failed, you should probably investigate what went wrong offline. In this case, I build a test stack with docker-compose in `app/integration` (for now, I had to do that only for plume and jitsi).