Hotfixes

What is a Hotfix?

A hotfix is a quick, targeted software update designed to address a specific issue or bug in a program. It's typically released outside of regular update cycles to fix urgent problems, such as security vulnerabilities, crashes, or critical bugs that affect the functionality of the software. Hotfixes are often applied to production environments without needing to go through the full release process, ensuring minimal disruption to users.

Hotfix Deployment Process in Feedier

1. Create a Pull Request (PR): Submit a PR with your hotfix to preprod (note: the branch name may vary with each Feedier version).
2. PR Review: The PR undergoes review and approval.
3. Merge the PR: After approval, merge your PR into preprod branch (note: the branch name may vary with each Feedier version).
4. Inform Prod-Team: After merged into preprod, inform the Prod-Team about it on slack channel #engineer-product-private, so they can test it.
5. Merge into Master: After you have the OK from the Prod-Team you need to merge your hotfix into master branch.
6. Verify with Prod-Team: After you merged your hotfix to the master branch you need to verify with the Prod-Team if you can deploy or if they are waiting for some other hotfix to be included on the deployment.
7. Create a Tag for the Hotfix: After verifying with Prod-Team, create a tag to identify the hotfixes and track the changes.
8. Deploy to Production: Once the tag is created, deploy the hotfix to the production environment.
9. Inform Prod-Team: After deployment, notify the Prod-Team on slack channel #engineer-product-private, so they can share the update on the appropriate Slack channels and stay informed about the deployment.

Deploy on V2

Create a Tag for Your Hotfix

1. Checkout the master/normal branch
   Use the following command to check out the master/normal branch:

   git fetch && git checkout master/normal

   or if you already had checked out the branch:

   git fetch && git switch master/normal && git pull

2. Check the last tag created on the master/normal branch
   Use the following command to check the last tag created on the branch:

   git describe --tags

3. Create the new tag
   Use the following command to create the new tag:

   git tag -a TAG_NAME -m YOUR_MESSAGE

   • TAG_NAME: Your new tag name. Ex: current tag name 3.34.2, your new tag will be 3.34.3.
   • YOUR_MESSAGE: Usually used to describe the changes on the tag

   Example: git tag -a 3.34.3 -m "Hot fix for FD-2229

4. Push the tag to the remote
   Use the following command to push the new tag to the remote server:

   git push origin TAG_NAME

   Example: git push origin 3.34.3

Start the deployment

Starting the deployment is a simple process; just click a link, and the deployment will begin. To obtain the deployment link, visit Forge website under Servers > feedier-production-1 > *.feedier.com > Deployments > Deployment Trigger URL.

Note: After you click the link a white page will open (don't panic!), it means it run successfully. You can check it on Forge under Servers > feedier-production-1 > *.feedier.com > Deployments > Deployment History.

Deploy on V3

Create a Tag for Your Hotfix

1. Checkout the master branch
   Use the following command to check out the master branch:

   git fetch && git checkout master

   or if you already had checked out the branch:

   git fetch && git switch master && git pull

2. Check the last tag created on the master branch
   Use the following command to check the last tag created on the branch:

   git describe --tags

3. Create the new tag
   Use the following command to create the new tag:

   git tag -a TAG_NAME -m YOUR_MESSAGE

   • TAG_NAME: Your new tag name. Ex: current tag name 3.34.2, your new tag will be 3.34.3.
   • YOUR_MESSAGE: Usually used to describe the changes on the tag

   Example: git tag -a 3.34.3 -m "Hot fix for FD-2229

4. Push the tag to the remote
   Use the following command to push the new tag to the remote server:

   git push origin TAG_NAME

   Example: git push origin 3.34.3

Start the deployment

Starting the deployment is a simple process; just click a link, and the deployment will begin. To obtain the deployment link, visit Forge website under Servers > feedier-production-1 > bx.feedier.com > Deployments > Deployment Trigger URL.

Note: After you click the link a white page will open (don't panic!), it means it run successfully. You can check it on Forge under Servers > feedier-production-1 > bx.feedier.com > Deployments > Deployment History.

Notes

• When deploying on the feedier-production-1 server, the deployment will also automatically occur on the feedier-production-1-uniform server.