In my last-post, we went over the deployment process in the EpiServer DXP environment. I mentioned that the next post would be related to using this within Azure DevOps, but I need to make a slight adjustment based on today’s update.
As of April 27th, 2020, EpiServer released their weekly update #313, which included a lot of enhancements for this Deployment API.
The IDC Technology Spotlight explores the rapidly changing commerce landscape and the top 5 benefits of a modern DXP.
In this post, we’re going to go through the following:
- The new features for the DXP Deployment API from this release
- How to use the scripts in my previous post, to take advantage of the sync-down
- How to build a script to export your environment database
As mentioned before, in the next part of this series we will cover how to set up a manual Release Pipeline to deploy into Integration.
This will eventually lead us to where we will be able to streamline the creation of a CI/DI Release Pipeline. This pipeline will publish all the way from Integration, to Preproduction, and finally to Production in an automated fashion that uses Episerver’s deployment process.