TechPrufer
Get started
Microsoft
Microsoft logoMicrosoft · Feature trail

CI/CD for Go Applications to Azure App Services

11 posts · Apr 2017 – Nov 2025

What this trail covers

This thread tracks the evolution of CI/CD for Go applications to Azure App Services, incorporating feature flags managed by Azure App Configuration for dynamic control of application features. This enables advanced deployment strategies like A/B testing and blue-green deployments, allowing for controlled rollouts and rollbacks. The integration facilitates managing application behavior and testing configurations without code redeployment. This post details best practices and anti-patterns for using Azure Developer CLI with layered infrastructure for deploying containerized applications to Azure Container Apps, enabling a "build once, deploy everywhere" pattern with separated container operations and layered infrastructure configuration.

All Microsoft trails
  1. Azure Developer CLI: Azure Container Apps Dev-to-Prod Deployment with Layered InfrastructureThis post introduces Azure Developer CLI v1.20.0's new capabilities for "build once, deploy everywhere" patterns with Azure Container Apps. It details `azd publish` for building and pushing containers to a registry, and `azd deploy --from-package` for deploying specific container versions without rebuilding. It also introduces the alpha feature of Layered Infrastructure, allowing sequential deployment of resources with dependency management and shared components like Azure Container Registry across environments. The post provides a Flask application example demonstrating this layered approach with separate resource groups for shared ACR, development, and production environments, and outlines the GitHub Actions workflow for build, dev deployment, and prod deployment.
  2. How to build, test and deploy your application using Azure and GitHubThis post provides a hands-on tutorial for building, testing, and deploying a Go web application to Azure App Services using GitHub Actions. It covers creating a multi-stage Docker image, setting up Azure Container Registry (ACR), building and pushing the Docker image to ACR, deploying the application to Azure App Services, and configuring a GitHub Actions workflow for CI/CD. It also includes steps for local testing of the Go application and its unit tests.
  3. Deploying Java Applications to Azure using Continuous DeliveryThis post details the CI/CD process for Java applications to Azure App Services using GitHub Actions, incorporating feature flags managed by Azure App Configuration for dynamic control of application features. It demonstrates how to troubleshoot a failed deployment by identifying a missing application setting (connection string for App Configuration) and resolving it. The post also highlights the ability to control features across multiple applications and environments using a single feature flag.
  4. Deploy a Java Application to Azure using Continuous IntegrationThis post demonstrates the integration of GitHub Actions for CI/CD pipelines to deploy a Java application to Azure App Service. It covers creating an Azure App Service from scratch, enabling GitHub Actions for continuous deployment, and troubleshooting a failed build due to a missing connection string. The post highlights the use of CodeSpaces for editing the GitHub workflow YAML file and syncing changes to trigger a successful build and deployment.
  5. Azure Friday: Best practices for Azure Container Instances (ACI) with GitHub ActionsThis post details best practices for Azure Container Instances (ACI) with GitHub Actions, focusing on security and developer-friendly automated workflows for running serverless containers in production. It covers avoiding public registries, using specific version tags, enforcing least privilege, and using container scanning tools. The integration with GitHub Actions is highlighted for its simplicity and ability to codify best practices into the release process.
  7. Azure Web App Service and GitHub Actions (Video Tutorial)This post introduces the integration of GitHub Actions with Azure Web App Service for CI/CD workflows. It highlights how to configure these workflows directly within the Azure portal's Deployment Center, eliminating the need to manually write YAML for basic setups. It also provides a sample React application repository for users to fork or clone and deploy to Azure Web App Service, demonstrating a stateless application deployment scenario.
  8. Create a CI/CD pipeline for your Azure IoT Edge solution with Azure PipelinesIntroduces the Azure IoT Edge task for Azure Pipelines, enabling CI/CD for IoT Edge solutions. The task provides capabilities to build module images, push them to container registries, and deploy them to Azure IoT Edge devices. It supports multi-platform builds (amd64, windows-amd64, arm32v7) and integrates with Azure IoT Hub for deployment management, including stages for different environments like QA and Production.
  9. Building and Deploying a Java Application to Oracle WebLogic Server Running in Azure VM with Microsoft Visual Studio Team ServicesThis post details the steps to configure a CI/CD pipeline in Visual Studio Team Services (VSTS) to build and deploy a Java EE application to Oracle WebLogic Server running on an Azure Virtual Machine. It covers setting up an agent pool, provisioning an Azure VM with necessary components (VSTS Build Agent, Oracle JDK, Apache Maven, Git), configuring Maven to access the Oracle Maven Repository, and modifying the Java application's POM file to include the WebLogic Maven plugin for deployment. The post emphasizes the flexibility of VSTS build/release definitions for custom deployment requirements.
  10. Deploy PHP application to Azure App Service using VSTSThis post details how to deploy a PHP application to Azure App Service using Visual Studio Team Services (VSTS). It covers forking a sample PHP app repository, creating an Azure Web App, setting up a release definition using the 'Deploy PHP App to Azure App Service' template, configuring the Azure App Service Deployment task with an Azure Service Connection and GitHub artifact source, and optionally using a deployment script for dependency updates. It also mentions the 'Take App Offline' option for resolving locked file issues.
  11. Deploy Node.js applications to Azure App ServiceThis post details how to deploy Node.js applications to Azure App Service using Visual Studio Team Services (VSTS) or Team Foundation Server (TFS). It outlines the steps for setting up a CI build definition, including installing npm dependencies, packaging the application with Gulp, and publishing the build artifact. It also describes how to create a release definition using the Azure App Service Deployment template, configuring the Azure subscription, App Service name, and deployment package. Specific configurations for generating web.config for Node.js applications using iisnode are also provided.
  12. Considerations on using Deployment Slots in your DevOps PipelineThis post details best practices and anti-patterns for using deployment slots in Azure App Service within DevOps pipelines. It highlights that deployment slots share resources, so load tests on a staging slot can impact production. It also warns against swapping slots across environments directly when databases or other dependencies are involved, as this only swaps the web application and can leave the system in an inconsistent state. The post advocates for creating separate web applications with matching App Service Plans for each environment (Dev, QA, Prod) and using deployment slots within each of these applications to mirror production behavior and catch issues before they reach production. It stresses the importance of backward-compatible database deployments to enable safe rollbacks.