Azure Stack 的混合式 CI/CD

當內部部署應用程式的建置和運作方式不同於雲端應用程式時,實作持續整合/持續開發 (CI/CD) 方法來部署應用程式會變得很困難。在 Azure 公用雲端與內部部署 Azure Stack 環境之間擁有一組一致的開發工具和程序,可讓組織更輕鬆地實作 CI/CD 實務。在 Azure 與 Azure Stack 中以適當方式部署的應用程式和服務,基本上可以互換並可在任一位置執行。

Hybrid CI/CD with Azure StackImplementing a continuous integration/continuous development (CI/CD) approach to deploying applications becomes difficult when on-premises applications are built and operated in different ways to cloud applications. Having a consistent set of development tools and processes across the Azure public cloud and on-premises Azure Stack environments makes it a lot easier for organisations 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.123455

工程師變更應用程式程式碼和 ARM 範本。

將程式碼和 ARM 範本簽入 Visual Studio Team Services Git。



同時部署到 Azure 與 Azure Stack 上的 App Service。

  1. 1 工程師變更應用程式程式碼和 ARM 範本。
  2. 2 將程式碼和 ARM 範本簽入 Visual Studio Team Services Git。
  3. 3 持續整合會觸發應用程式組建與單元測試。
  1. 4 持續部署觸發程序會協調應用程式構件的部署與環境專屬的參數。
  2. 5 同時部署到 Azure 與 Azure Stack 上的 App Service。



Hybrid identity with Azure StackThe need to keep application components on-premises doesn’t have to be a barrier to adopting cloud technologies. With Azure Stack, app components can reside on-premises while interacting with components running in Azure public cloud. This blueprint enables teams to manage identity for users as well as applications in a way that is consistent across clouds.12334556

Azure Stack 的混合式身分識別

在內部部署保留應用程式元件的需求,不一定會成為採用雲端技術的障礙。有了 Azure Stack,應用程式元件可以位於內部部署,同時與 Azure 公用雲端中執行的元件互動。此藍圖可讓小組在雲端之間一致地管理使用者身分識別與應用程式。