How to manage hotfix resolution?

[mawd]

When pushing to production sometimes we can have blocking issu that needs to be fix ASAP.

I believe that it is a best practice to have a bugfix sandbox aligned with the production and staging environment to achieve it.

Bellow is a schema of my vision.

What is your recommandation to handle this kind of need ? How to keep the developer sandboxes update to date in this case?

[ssetayeshfar]

Hi @mawd,

We know that the "hot fix" flow is valid and while we don't have this specifically supported in DevOps Center today we have plans to support it more robustly in a future release.

Our recommendation for the time being is to create a work item to track the changes and ultimately move the changes through the full pipeline. So if you know that a hot fix happened at some point in the pipeline, you can recreate that fix in a dev environment and via a work item and move it through the pipeline after the fact, that will keep things in sync.

We're also looking at being able to detect the change automatically as it's introduced to a downstream branch (if it came in that way) and provide guidance/help in creating a work item and back-porting the changes to the earlier stages. We ultimately want to always have a work item to track changes, regardless of where they got introduced in the flow.

Philosophically, we are always trying to keep stage branches and orgs in sync, and we want all changes to move left to right through the pipeline as part of a work item. That said, as mentioned above, we do acknowledge that the Hot Fix situation needs to be accounted for, and so we are looking at ways to facilitate getting the project back aligned to this overall philosophical approach after the hot fix has happened.

Please let us know if you have other thoughts, feedback or questions. What I explained above is also documented here.

Thank you.