Loading...
Area: Episerver DXC Service
Applies to versions: Not applicable

Deploy using code packages

Deploying using a code package is the default and recommended a way to use the deployment API. This gives the flexibility to deploy code to any target environment without needing to deploy to a source environment and then promote it. This is also Episerver's way of allowing hotfix deployments to the Production environment without needing to disrupt the existing code running in non-production environments. 

The process of deployment is as follows:

  1. Create a code package for your application.
  2. Upload the code package to a package repository in your DXC environment.
  3. Start deployment of the package to a Web App slot.
  4. Track deployment status until the first stage of deployment is completed.
  5. Verify the site on the slot (manually or using automated smoke tests).
  6. Complete or Reset deployment depending on the verification results.

Note that it is possible to deploy code package to the Integration environment directly using Deployment API instead of the conventional way of publishing the code from Visual Studio. However note that when you do so, config transformation will be applied on the code deployed to Integration if the deployment engine sees a valid transformation file to apply.

For example, if there is a Web.Integration.config, it will be processed as part of the deployment flow. This is similar to when you deploy code from Integration to another environment using DXC service management portal.

Last updated: Oct 17, 2019