World is now on Opti ID! Learn more

Ronil Rangaiya
Jun 22, 2022
  23
(0 votes)

Deployment API and multi-stage YAML pipelines - an update

Recap

It has been almost 2 years since my last blog on reusable multi-stage YAML pipelines to manage Optimizely DXP deployments.

A lot has changed since then so wanted to take the opportunity to give them a much needed update.

To recap, I created these portable YAML pipelines to use across projects for quick and consistent setup of CI/CD workflows. These pipelines directly use the EpiCloud Powershell module so you have full control and access to the scripts if you need to change anything to fit your requirements or quickly leverage any updates to the EpiCloud module.

What's New?

The following changes have been made to the YAML pipelines

  • The `Integration` pipeline updated to support direct deploy to the Integration environment using the code package approach. 
  • The old Integration pipeline renamed to `Integration-WebDeploy` for deploying using the Azure App Service Deploy method. This is provided for legacy purposes and can be used to deploy to an additional DXP environment that serves as the Development / Integration environment.
  • The 'Release` pipeline updated to support Smooth / Zero downtime deployments
  • The `Release` pipeline updated to allow for manual validation step before completing Production deployment
  • Support for variable groups
  • Added runtime parameters

What about .Net 5?

While the pipelines currently don't support .Net 5 build process, they can be easily repurposed for a .Net 5 / CMS 12 project. Apart from the build and publish commands, the rest of the processes should be the same. Otherwise stay tuned for .Net 5 YAML pipelines in the next update.

Summary

Traditionally, the Azure DevOps Classic UI editor is preferred for build and release pipelines. However, there are some benefits to using YAML pipelines including source-controlled pipeline files and having a unified view of your build and deployment processes. Read more about the differences between YAML and Classic pipelines and decide if YAML suits your DevOps approach.

For the latest pipeline files and documentation, please refer to my GitHub repository

I'd love to get any feedback/comments/questions.

Jun 22, 2022

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |