Hybrid CI/CD

Solution Idea

If you'd like to see us expand this article with more information (implementation details, pricing guidance, code examples, etc), let us know with GitHub Feedback!

Implementing a continuous integration/continuous development (CI/CD) approach to deploying applications becomes difficult when on-premises applications are built and operated in different ways than cloud applications. Having a consistent set of development tools and processes across the Azure public cloud and on-premises Azure Stack environments makes it far easier for organizations to implement a practice of CI/CD. Apps and services deployed the right way in Azure and Azure Stack are essentially interchangeable and can run in either location.

Architecture

1 2 3 4 5 5

Engineer makes changes to application code and ARM template.

Code and ARM template are checked into Visual Studio Team Services Git.

Continuous integration triggers application build and unit tests.

Continuous deployment trigger orchestrates deployment of application artifacts with environment-specific parameters.

Deployment to App Service on both Azure and Azure Stack.

Data Flow

  1. Engineer makes changes to application code and ARM template.
  2. Code and ARM template are checked into Visual Studio Team Services Git.
  3. Continuous integration triggers application build and unit tests.
  4. Continuous deployment trigger orchestrates deployment of application artifacts with environment-specific parameters.
  5. Deployment to App Service on both Azure and Azure Stack.

Components

  • Azure Stack is a hybrid cloud platform that lets you use Azure services on-premises
  • Step-by-step guidance: Step-by-step guidance
  • Azure DevOps: Build and deploy multi-platform apps to get the most from Azure services
  • Web Apps: Quickly create and deploy mission critical Web apps at scale.

Next Steps