This topic describes continuous deployment of code changes from your local development environment to the Integration environment in Episerver DXC Service.
When is this applicable?
Follow this procedure for an existing site running in the Integration environment, to which you want to deploy code updates. This can be done incrementally to upgrade your site during the development process, after a first-time deployment. See DXC Service self-deployment guide.
You can deploy code changes continuously using either deployment tools for a version controlled source code, or through Visual Studio using the Episerver extensions and publish profiles. In both cases you need to contact Episerver before you deploy for the first time, to get the needed deployment integration settings information.
If you work in a development team using version control for your source code, you can use any deployment tool that supports Azure Resource Manager (ARM), for example Octopus Deploy, Visual Studio Team Services or TeamCity.
See Continuous deployment of Episerver solutions for an example using Octopus Deploy.
Follow the steps below to initiate the setup of the deployment integration for your environment.
In this example we will deploy code changes for a Commerce solution, which has two sites (front-end/back-end). The steps are the same for a solution with only CMS, in this case you will only have one site.
When using the setting Remove additional files at destination, be careful not to touch the files stored in the newrelic folder. To avoid issues with these files being removed or blocked during publish, you can edit either the publish profile or project file, and add the following settings:
<Target Name="AddCustomSkipRules"> <ItemGroup> <MsDeploySkipRules Include="SkipFilesFolder"> <AbsolutePath>newrelic</AbsolutePath> </MsDeploySkipRules> </ItemGroup> </Target>
Note: ensure that the Apps folder is included in your Commerce Manager project.
Last updated: Feb 04, 2019