Skip to content

ci: Added Deployment v2 pipeline with Windows and Linux support#686

Merged
Prajwal-Microsoft merged 1 commit into
mainfrom
psl-deploymentPipelineChanges
Dec 5, 2025
Merged

ci: Added Deployment v2 pipeline with Windows and Linux support#686
Prajwal-Microsoft merged 1 commit into
mainfrom
psl-deploymentPipelineChanges

Conversation

@Vamshi-Microsoft

Copy link
Copy Markdown
Contributor

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:

  • Added a new orchestrator workflow (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.
  • Introduced platform-specific entry workflows: deploy-linux.yml and deploy-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:

  • Added a dedicated cleanup job workflow (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:

  • All workflows now support a wide range of input parameters, including Azure location, resource group name, WAF and EXP toggles, Docker build options, resource cleanup, test suite selection, and resource IDs. This makes the deployment process highly customizable and adaptable to different environments and scenarios. [1] [2] [3]

Testing and Notification Integration:

  • The orchestrator workflow includes jobs for running end-to-end tests and sending notifications about deployment and test results, improving visibility and reliability of the deployment process.

These changes significantly improve the maintainability, scalability, and clarity of the deployment automation for the project.

  • Workflow Orchestration

    • Added deploy-orchestrator.yml to coordinate build, deploy, test, notification, and cleanup jobs with parameter passing and conditional execution.
    • Created deploy-linux.yml and deploy-windows.yml as entry points for platform-specific deployments, supporting various triggers and input options. [1] [2]
  • Resource Cleanup

    • Added job-cleanup-deployment.yml for secure, asynchronous Azure resource group deletion and job summary reporting.
  • Parameterization

    • Enhanced workflows with extensive input options for deployment customization (location, resource group, features, test suite, resource IDs, etc.). [1] [2] [3]
  • Testing & Notification

    • Integrated end-to-end test execution and deployment/test result notification jobs into the orchestrator workflow.

Does this introduce a breaking change?

  • Yes
  • No

@Prajwal-Microsoft Prajwal-Microsoft merged commit e2617fc into main Dec 5, 2025
9 checks passed
@github-actions

github-actions Bot commented Dec 5, 2025

Copy link
Copy Markdown

🎉 This PR is included in version 3.1.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

@Harmanpreet-Microsoft Harmanpreet-Microsoft deleted the psl-deploymentPipelineChanges branch January 2, 2026 08:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants