Episerver DXP content harmonization with Epinova DXP deployment
Harmonize content between Episerver DXP environments from Azure DevOps with Epinova DXP Deployment Extension. Without using a single line of PowerShell.
What is Epinova DXP deployment extension?
Epinova DXP deployment extension contains Azure DevOps tasks that abstract the interaction with the Episerver DXP deployment API. If you would like or need to know more about the basics you can read it in my earlier blog post “Epinova DXP deployment extension for Azure DevOps Part 1 - Introduction”.
But very shortly we can say that with Epinova DXP deployment tasks enables you to use the functionality in the Episerver DXP deployment API without having to write any PowerShell.
How to harmonize content between Episerver DXP environments in Azure DevOps?
There are two ways that you can set this up. Either you like to use YAML to create a pipeline that copy your content or you like to setup a release pipeline in classic mode. Both ways are supported.
It as simple as just using the task “Content copy” to solve this.
If you are already using Epinova DXP deployment extension there is a good possibility that you have already done this. But you need to have the following steps setup.
Install Epinova DXP deployment extension to you Azure DevOps organization
Instructions how to install the extension and be able to use the tasks can be found in the documentation. https://github.com/Epinova/epinova-dxp-deployment/tree/master
DXP variable group
Either you choose the YAML or classic road you need to make sure that you have created a “Variable group” with your project specific variables. You can follow the instructions in the documentation how to create variable group and how to gather the variable information needed. https://github.com/Epinova/epinova-dxp-deployment/blob/master/documentation/CreateVariableGroup.md
Content copy with YAML
There are 4 example YAML files in the documentation that can be downloaded and used from the GitHub repository.
The 1:st example, “Copy-PrepInte.yml”, can be used out of the box if you want to copy content (DB and blobs) from preproduction to integration environment.
The 2:nd example, “Copy-ProdInte.yml”, can be used out of the box if you want to copy content (DB and blobs) from production to integration environment.
The 3:rd example, “Copy-ProdPrep.yml”, can be used out of the box if you want to copy content (DB and blobs) from production to preproduction environment.
The 4:th example, “Copy-ProdPrepInte.yml”, can be used out of the box if you want to copy content (DB and blobs) from production to preproduction and to integration environment.
You can find ready to use examples here
(See all YAML example pipelines https://github.com/Epinova/epinova-dxp-deployment/tree/master/Pipelines)
There is no automatic trigger on these pipelines and they should be started manually when needed.
How to add a YAML pipeline
- Download one of the example YAML files from GitHub or create your own YAML file. In this example I have a “pipeline” folder in the root of the project where I place the YAML pipelines.
- Check in/Commit and push your added YAML file to your code repository.
- In Azure DevOps, go to the Pipeline list page and click on “New pipeline”.
- Select the type of your repository.
- Select the repository. (This could be little different depending on which repository type you are using.)
- When you get to the step to choose “pipeline”. Select “Existing Azure Pipelines YAML file”.
- Select the YAML file you have added before. Azure DevOps have scanned your folders and will present all the YAML files that it can find in your source code.
- You should now be able to see the YAML code and can rename the pipeline and/or start the pipeline.
Content copy - classic mode
It does not matter if you have YAML files for deployment or not. Sometimes it is much simpler to have some pipelines in classic mode.
- Create a new release pipeline in you project.
- Select “Empty job” and give the pipeline a good name.
- Name the first stage. Example: “Prod2Prep”
- Create another stage and name it. Example: “Prod2Inte”.
- Before we add tasks to the stages we should link the release pipeline to the variable group with our variables that we can reuse. Click the “Variables” tab and select the “Variable groups”. Click “Link variable group” and select your variable group that you created earlier.
- Go back to the first stage. Now it is time to start add the tasks.
- Click the plus sign/icon and search for DXP in the search field. All Epinova DXP deployment tasks will be shown and you should add the “Content copy” task.
- Now just specify the “Environment”, “Include BLOB” and “Include DB”.
- Now you can do the same thing for the “Prod2Inte” stage. But make sure that you set “Environment” = Production => Integration.
You are done. You can now run the release pipeline and harmonize the content for your DXP website from production => preproduction and production => integration. After you run the content copy you can see in the log what the task has done. This is an example of that:
It is also possible to configure the stages to have post and/or pre-approvals. Or add a scheduler that trigger the release pipeline reoccurring. It is all up to you and your project.
I hope that this was helpful and that you realize that you can setup and use the Episerver DXP deployment APIs without writing a single line of PowerShell.
For the latest documentation and guides please visit the repo on GitHub. Where all code, documentation and YAML files etc. exist.