Loading...
Area: Episerver Customer-Centric DXP
Applies to versions: Not applicable

Deploying code changes

Recommendations [hide]

This topic describes the continuous deployment of code changes from your local development environment to the Integration environment in Episerver DXP

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 DXP self-deployment guide.

Deployment methods

You can deploy code changes continuously using either Deployment API or using deployment tools for version-controlled source code.

Before you start

  • See Requirements for recommended versions of software, tools and services to use.
  • See Getting started for information needed to deploy.

Deploying using Deployment API

Deploying the code changes using the Deployment API is currently the recommended approach for publishing application code to a DXP Environment. See Deployment API for an overview and instructions on how to use the API. 

Deploying from a version-controlled environment 

If you work in a development team using version control for your source code, you can use any deployment tool such as Octopus Deploy, Visual Studio Team Services or TeamCity. See Azure DevOps and Episerver deployment API  (blog post by Anders Wahlqvist) for instructions on how to integrate Deployment API to CI/CD pipeline such as Azure DevOps. 

DeployOctopus.png

Related topics

Do you find this information helpful? Please log in to provide feedback.

Last updated: Apr 02, 2020

Recommendations [hide]