ci: Added Deploy-v2-windows workflow to support the local deployment scenarios #330
Conversation
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
Vamshi-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft and
aniaroramsft
as code owners
| @@ -0,0 +1,867 @@ | |||
| name: Deploy-Test-Cleanup (v2) Windows | |||
Contributor
There was a problem hiding this comment.
Can we have the common steps into seperate yaml files and refer them, which reduces the maintenance of them
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 improvements to CI/CD automation and developer experience by making the workflow more robust and enhancing integration with GitHub Actions. The most notable changes are grouped below:
CI/CD Workflow Improvements:
continue-on-error: trueto a job in.github/workflows/deploy-v2.ymlto allow the workflow to proceed even if this job fails, increasing robustness in deployment pipelines.GitHub Actions Integration:
register_schema.ps1to set GitHub Actions outputs for schema IDs when running in a GitHub Actions environment, enabling downstream jobs to consume these outputs. The script now generates safe variable names from class names and appends them to the$GITHUB_OUTPUTfile.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation