From 3650dc65a942c5007c1e604ef0e724754be36109 Mon Sep 17 00:00:00 2001 From: Oliver Davies Date: Fri, 23 Jun 2023 13:08:44 +0100 Subject: [PATCH] daily-email: add 2023-06-20 Should you deploy on a Friday? --- src/content/daily-email/2023-06-20.md | 29 +++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 src/content/daily-email/2023-06-20.md diff --git a/src/content/daily-email/2023-06-20.md b/src/content/daily-email/2023-06-20.md new file mode 100644 index 00000000..5bb6fa25 --- /dev/null +++ b/src/content/daily-email/2023-06-20.md @@ -0,0 +1,29 @@ +--- +title: > + Should you deploy on a Friday? +pubDate: 2023-06-20 +permalink: > + archive/2023/06/20/should-you-deploy-on-a-friday +tags: + - deployments +--- + +There's a common saying about not deploying changes on a Friday to prevent outages or issues before the weekend. + +I've also seen this where people won't deploy after a particular time of the day as it's too close to the evening. + +## When did you last deploy? + +The longer it's been since the last deployment, the risker each deployment is. + +If there are weeks or months of changes, it will be risky regardless of which day it is. + +If your last deployment was an afternoon, deploying a small change the following morning will be low risk, even on a Thursday and Friday. + +## Conclusion + +If you're nervous about deploying on a Friday, I think you need to aim for smaller and more frequent deployments to minimise the risk. + +The issue isn't when you're deploying. You likely need to do so more often. + +If there is an issue after a large release, it will take more time to debug or roll back compared to a small release which is easier to find and fix the problem or revert that single change.