In recent months, we’ve seen many Sitecore hotfixes and security patches. While essential, applying these updates—first locally and then through your DevOps pipeline—can quickly become confusing without a proper setup. To ensure your patches are applied consistently, tracked effectively, and deployed securely, you need a structured approach baked into your solution. In this post, I’ll walk you through how to manage Sitecore hotfixes the right way. Interested? Let’s dive in.
SECURITY HOTFIXES MANAGEMENT
If you're getting a new task to apply a security patch for sitecore, you may start thinking what would be the best approach to do that, should I install the package directly into the different environments, should be a package installation or manual, if package what should I do for content delivery (CD) server, maybe you start thinking about including the patch files in solution code, one step on the right direction, should you reference or add these files into a main project or security patches project, ok, have these files got published successfully locally and on DevOps CI/CD pipelines, or did they got ignore because they are not used?! too many things to consider, but I will show you a good way to overcome all these issues. keep reading!!
The solution I have in a combination of two great features, xcopy and target, xcopy is used to Copy files and directories, including subdirectories, you can get more information about this on MS documntation, link cab be found in references.
The other feature is an MsBuild feature, Targets group tasks together in a particular order and allow the build process to be factored into smaller units. For example, one target may delete all files in the output directory to prepare for the build, while another compiles the inputs for the project and places them in the empty directory, in our case we're using it for after build of execution of xcopy, more information can be found on MS documentation, link can be found in references.
Now all what you need to do is to create a trackable folder under your solution, as example a folder called "Hotfixes", where you can use the folder to place any new hotfix patches you get, then use the below sample of how to manage Sitecore hotfixes within your project file:
Hopefully the above helps someone to better manage Sitecore hotfixes, below are references to get more information:
No comments:
Post a Comment