| title | Using a hotfix production environment |
|---|---|
| description | Learn how to use a hotfix production environment with continuous integration and delivery in Azure Data Factory pipelines. |
| ms.subservice | ci-cd |
| author | kromerm |
| ms.author | makromer |
| ms.reviewer | whhender |
| ms.topic | how-to |
| ms.date | 01/29/2025 |
[!INCLUDEappliesto-adf-xxx-md]
If you deploy a factory to production and realize there's a bug that needs to be fixed right away, but you can't deploy the current collaboration branch, you might need to deploy a hotfix. This approach is as known as quick-fix engineering or QFE.
Use the following steps to deploy a hotfix in your production and test environments.
-
In Azure DevOps, go to the release that was deployed to production. Find the last commit that was deployed.
-
From the commit message, get the commit ID of the collaboration branch.
-
Create a new hotfix branch from that commit.
-
Go to the Azure Data Factory Studio and switch to the hotfix branch.
-
By using the Azure Data Factory Studio, fix the bug. Test your changes.
-
After the fix is verified, select Export ARM Template to get the hotfix Resource Manager template.
-
Manually check this build into the adf_publish branch.
-
If you've configured your release pipeline to automatically trigger based on adf_publish check-ins, a new release will start automatically. Otherwise, manually queue a release.
-
Deploy the hotfix release to the test and production factories. This release contains the previous production payload plus the fix that you made in step 5.
-
Add the changes from the hotfix to the development branch so that later releases won't include the same bug.
See the video below an in-depth video tutorial on how to hot-fix your environments.
[!VIDEO https://learn-video.azurefd.net/vod/player?id=b0bab151-85b7-4684-a184-ec5e6b972415]
- Automated publishing for continuous integration and delivery
- Continuous integration and delivery overview
- Automate continuous integration using Azure Pipelines releases
- Manually promote a Resource Manager template to each environment
- Use custom parameters with a Resource Manager template
- Linked Resource Manager templates
- Sample pre- and post-deployment script