85 lines
3.2 KiB
YAML
85 lines
3.2 KiB
YAML
uuid:
|
|
- value: 71802d07-348e-45af-9fed-f4f8232b9142
|
|
langcode:
|
|
- value: en
|
|
type:
|
|
- target_id: daily_email
|
|
target_type: node_type
|
|
target_uuid: 8bde1f2f-eef9-4f2d-ae9c-96921f8193d7
|
|
revision_timestamp:
|
|
- value: '2025-05-11T09:00:38+00:00'
|
|
revision_uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
revision_log: { }
|
|
status:
|
|
- value: true
|
|
uid:
|
|
- target_type: user
|
|
target_uuid: b8966985-d4b2-42a7-a319-2e94ccfbb849
|
|
title:
|
|
- value: |
|
|
Should you deploy on a Friday?
|
|
created:
|
|
- value: '2023-06-20T00:00:00+00:00'
|
|
changed:
|
|
- value: '2025-05-11T09:00:38+00:00'
|
|
promote:
|
|
- value: false
|
|
sticky:
|
|
- value: false
|
|
default_langcode:
|
|
- value: true
|
|
revision_translation_affected:
|
|
- value: true
|
|
path:
|
|
- alias: /daily/2023/06/20/should-you-deploy-on-a-friday
|
|
langcode: en
|
|
body:
|
|
- value: |
|
|
<p>There's a common saying about not deploying changes on a Friday to prevent outages or issues before the weekend.</p>
|
|
|
|
<p>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.</p>
|
|
|
|
<h2 id="when-did-you-last-deploy%3F">When did you last deploy?</h2>
|
|
|
|
<p>The longer it's been since the last deployment, the risker each deployment is.</p>
|
|
|
|
<p>If there are weeks or months of changes, it will be risky regardless of which day it is.</p>
|
|
|
|
<p>If your last deployment was an afternoon, deploying a small change the following morning will be low risk, even on a Thursday and Friday.</p>
|
|
|
|
<h2 id="conclusion">Conclusion</h2>
|
|
|
|
<p>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.</p>
|
|
|
|
<p>The issue isn't when you're deploying. You likely need to do so more often.</p>
|
|
|
|
<p>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.</p>
|
|
|
|
|
|
format: full_html
|
|
processed: |
|
|
<p>There's a common saying about not deploying changes on a Friday to prevent outages or issues before the weekend.</p>
|
|
|
|
<p>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.</p>
|
|
|
|
<h2 id="when-did-you-last-deploy%3F">When did you last deploy?</h2>
|
|
|
|
<p>The longer it's been since the last deployment, the risker each deployment is.</p>
|
|
|
|
<p>If there are weeks or months of changes, it will be risky regardless of which day it is.</p>
|
|
|
|
<p>If your last deployment was an afternoon, deploying a small change the following morning will be low risk, even on a Thursday and Friday.</p>
|
|
|
|
<h2 id="conclusion">Conclusion</h2>
|
|
|
|
<p>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.</p>
|
|
|
|
<p>The issue isn't when you're deploying. You likely need to do so more often.</p>
|
|
|
|
<p>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.</p>
|
|
|
|
|
|
summary: null
|
|
field_daily_email_cta: { }
|