MI 1.1 Hotpatch process
A “hotpatch” describes a patch made to a release that is not a tagged patch release. It can be used to temporarily ship a specific commit for a small number of services to a particular Cloud instance.
This process should only be used if waiting for a tagged release or requesting a tagged patch release is not viable.
Creating a hotpatch
The team requesting that a hotpatch be shipped to a Cloud customer should create patched images for the relevant services:
- Create a branch from the latest
- Cherry-pick the relevant changes into your branch
sg ci build docker-images-patch $SERVICEfor the relevant services
- Find the built image tags in the build results
They should then create an issue in
- Reason for the hotpatch
- The target customer instance
- The hotpatched image tag(s) to deploy
- Link to the branch from which the hotpatched images are built
Deploying a hotpatch
Create an override in
$CUSTOMER/overrides if it exists, or directly in
version: '2.4' services: frontend: image: $IMAGE
mi sync artifacts
When a hotpatch is deployed, it must be removed as part of the next release upgrade.