hotfix
An urgent, unplanned change deployed to repair a problem in production.
In more detail
Because it cannot wait for the next planned release, a hotfix is usually made on its own branch from the released version, then merged back so the fix is not lost. It often skips part of the normal release process because of the urgency. A deployment that needs a hotfix counts towards change fail rate, and the hotfix deployment itself counts as rework.
Examples
In Git Flow, hotfix branches start from main and merge back into both main and develop.git worktree add ../hotfix fix-bugRelated terms
- deployment rework rate — The share of deployments that are unplanned and happen because of an incident in production.
- change fail rate — The share of deployments that need immediate intervention afterwards, usually a rollback or a hotfix.
- remediation — The act of fixing a problem, such as putting back a configuration or shipping a fix after a failed deployment.
- fix forward — Recovering from a bad change by quickly shipping a new fix, instead of going back to the previous version.
- Git Flow — A branching model published by Vincent Driessen in 2010 with long-lived main and develop branches plus feature, release and hotfix branches.
- configuration drift — The slow, unrecorded way machines end up with different versions and settings from each other.
- change management — The process of proposing, reviewing, approving and recording changes to systems, with a plan to undo them.
- git worktree — A command that checks out another branch into a separate folder that shares the same repository, so you can work on two branches at once.
Taught in
- Deploying With Less Downtime — Microsoft Azure DevOps Engineer Expert (AZ-400) Exam Prep
- A Hotfix At 3 A.M.: Who Wins At 3:05? — Certified GitOps Associate (CGOA) Exam Prep
- Terminology Sprint: One Incident, Nine Terms — Certified GitOps Associate (CGOA) Exam Prep
- Seven Steps Called GitOps: The Declarative Principle — Certified GitOps Associate (CGOA) Exam Prep
- Twelve Keys To Production: Pulled Automatically — Certified GitOps Associate (CGOA) Exam Prep
- DORA Metrics: Measuring Your Pipeline — Continuous Integration & Continuous Delivery Pipelines
- Feature Flags and DORA Metrics — Continuous Integration & Continuous Delivery Pipelines
- Continuous IaC Drift Detection & State Protection — Cloud Security & DevSecOps Engineering
- Instability: Change Fail Rate And Deployment Rework Rate — DevOps & Site Reliability Engineering
- Trunk-Based Development Versus Git Flow — DevOps & Site Reliability Engineering
- Investigating History: blame, bisect And worktree — Advanced Git Internals & Distributed Workflows
- Trunk Based Development Versus Git Flow — Advanced Git Internals & Distributed Workflows
- Two Versions Of The Truth: GitOps, Helm And Kustomize — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
References
- DORA: DORA's software delivery performance metrics
- Vincent Driessen: A successful Git branching model
- Martin Fowler: Patterns for Managing Source Code Branches
- NIST glossary: patch