ci: Added Deployment v2 pipeline with Windows and Linux support#686
Merged
Conversation
Prajwal-Microsoft
approved these changes
Dec 5, 2025
|
🎉 This PR is included in version 3.1.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Purpose
This pull request introduces a new modular and orchestrated approach to deployment workflows for both Linux and Windows environments, with enhanced support for resource cleanup, end-to-end testing, and notification handling. The changes primarily add new workflow files and jobs, replacing previous monolithic deployment processes with a more maintainable and flexible structure.
Deployment Workflow Orchestration:
deploy-orchestrator.yml) that coordinates Docker build, deployment, end-to-end testing, notification, and cleanup jobs. This workflow passes parameters between jobs and supports both Linux and Windows runners, enabling more granular control over the deployment pipeline.deploy-linux.ymlanddeploy-windows.yml, which trigger the orchestrator with appropriate runner OS and input parameters. The Linux workflow supports scheduled and workflow-run triggers, while the Windows workflow currently supports manual dispatch only. [1] [2]Resource Cleanup Automation:
job-cleanup-deployment.yml) that securely logs into Azure, initiates asynchronous resource group deletion, and generates a detailed job summary for monitoring cleanup status. This job is triggered conditionally after successful deployments and supports both OS platforms.Parameterization and Flexibility:
Testing and Notification Integration:
These changes significantly improve the maintainability, scalability, and clarity of the deployment automation for the project.
Workflow Orchestration
deploy-orchestrator.ymlto coordinate build, deploy, test, notification, and cleanup jobs with parameter passing and conditional execution.deploy-linux.ymlanddeploy-windows.ymlas entry points for platform-specific deployments, supporting various triggers and input options. [1] [2]Resource Cleanup
job-cleanup-deployment.ymlfor secure, asynchronous Azure resource group deletion and job summary reporting.Parameterization
Testing & Notification
Does this introduce a breaking change?