forcedotcom
Hotfix use-case
Fast-track a fix to a production issue, while keeping your pipeline in sync.
@kfidelak94 Could you please elaborate more on this? Let’s say Salesforce Admin modify layout and profile in production for speed because they are business critical fix. How can the all env in your pipeline be kept in sync?
That is a common scenario for us. We often times have mission critical things that are done in production but need to be pushed down to lower environments so the pipeline is all in sync. We also have some integrations like our phone system that does not work in sandboxes so we often times have to do our testing for those things live in production. Obviously not ideal but it happens.
It is also common to have to sync the WI created in another project and that has already reached production.
It'd be awesome if either the last environment before production could have two environments (one a hotfix) or if a dev box can be nominated to do special hotfix deployments that go into production. That way the fixes can be in the same project/pipeline/repo.
Hi, I have a very standard pipeline, but I need a Hotfix sandbox to develop hotfixes, push them tp Pord and back-promote them to rest of the pipeline. Not being able to accomodate this requirement is causing problem from adoption by our clients... Would you have a temp solution until you implement a final one in DC ? Regards, Patrick
We've been pondering how to do this as well, so I'm upvoting this idea. It would be great to have a seamless way to fast track maintenance hotfixes to production, and then have them reflected in our project pipeline.
We do have this hotfix scenario happen almost on a weekly basis and trying to find a way to update this as we are transitioning to DevOps Center. Upvoting this idea. Anyone has a workaround, approach or a process that is being used when changes go from multiple stages.
