Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
​Application Lifecycle Management on Microsoft Power Platform

You're reading from   ​Application Lifecycle Management on Microsoft Power Platform A comprehensive guide to managing the deployment of your solutions

Arrow left icon
Product type Paperback
Published in Oct 2024
Publisher Packt
ISBN-13 9781835462324
Length 222 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Benedikt Bergmann Benedikt Bergmann
Author Profile Icon Benedikt Bergmann
Benedikt Bergmann
Arrow right icon
View More author details
Toc

Table of Contents (17) Chapters Close

Preface 1. Chapter 1: An Intro to ALM FREE CHAPTER 2. Chapter 2: ALM in Power Platform 3. Chapter 3: Power Platform Environments 4. Chapter 4: Dataverse Solutions 5. Chapter 5: Power Platform CLI 6. Chapter 6: Environment Variables, Connection References, and Data 7. Chapter 7: Approaches to Managing Changes in Power Platform ALM 8. Chapter 8: Essential ALM Tooling for Power Platform 9. Chapter 9: Project Setup 10. Chapter 10: Pipelines 11. Chapter 11: Advanced Techniques 12. Chapter 12: Continuous Integration/Continuous Delivery 13. Chapter 13: Deepening ALM Knowledge 14. Assessments 15. Index 16. Other Books You May Enjoy

Release pipeline

The last pipeline is the release pipeline. Since the goal is to deploy with one pipeline run to different environments, this pipeline will be a bit more complex than the other two. We have to use different stages for different environments.

ADO

We also have to configure the build pipeline as a resource so that we can reuse the created solution file artifact.

To achieve this, we replace the whole file with the following YAML:

trigger: none
pr: none
resources:
  pipelines:
    - pipeline: buildPipeline
      source: 'Build Solution'
      trigger: none
stages:

In the resources part, it is important that the value of the source parameter exactly matches the name of your build pipeline.

After that, there is a setup per stage. Usually, we at least have Test and Production, but there could be other environments in between or after that. For example, a UAT...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image