How to deploy to Standard or Azure environments in Release Management 2013 with Update 3 RC
Jul 7, 2014Roopesh Nair
Summary
This post details the use of Release Management 2013 Update 3 RC for agent-less deployments to Standard (on-premises) and Azure environments using PowerShell and Desired State Configuration (DSC). It outlines the prerequisites for PowerShell and DSC, the steps for authoring deployments in both Standard and Azure environments, and the configuration parameters for server name, credentials, script paths, and secure connections (CredSSP, UseHTTPS, SkipCaCheck). It also highlights differences between the vNext release pipeline and agent-based pipelines, noting unsupported features like rollback controls within other flow controls and WinRM session timeouts requiring manual configuration.
More from the Azure DevOps Pipelines for Dev-to-Prod Promotion trail
- Azure Developer CLI: From Dev to Prod with Azure DevOps Pipelines
- Azure Developer CLI: From Dev to Prod with One Click
- February Patches for Azure DevOps Server
- Revolutionizing Requirement Gathering: Azure DevOps Meets Azure OpenAI using Semantic kernel
- Deploy a Java application to Azure App Service using GitHub Actions