On Prem To the Cloud: Let's Rub Some DevOps On It! (Ep 3)
May 13, 2021Damian Brady

Summary
This post demonstrates how to apply DevOps practices, specifically CI/CD pipelines using Azure Pipelines and GitHub Actions, to a "legacy" application that has been migrated to the cloud. It details the process of configuring a YAML pipeline for continuous integration (building, testing, packaging) and continuous deployment (deploying to virtual machines). Key tasks highlighted include using the 'Publish Pipeline Artifact' task, setting up 'Environments' in Azure Pipelines with VM resources, and deploying applications using the 'Deploy SQL Dacpac Deployment Group' and 'IIS Web Application Deployment' tasks. For GitHub Actions, it notes the use of self-hosted runners and the need to find alternative actions for IIS and DACPAC deployment.
More from the Azure Pipelines Agent Operating System Support trail
- April Patches for Azure DevOps Server and Team Foundation Server
- CDN Domain URL change for Agents in Pipelines
- Announcing the General Availability of Managed DevOps Pools (MDP) for Azure DevOps
- Announcing Public Preview of Managed DevOps Pools (MDP) for Azure DevOps
- End of support for Azure Pipelines agents running on CentOS 6, Debian 4.9, Fedora 32, Ubuntu 16, macOS 10.14, and older versions