Initial scaffold of new release pipeline in Azure Pipelines #386
Conversation
This file contains 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
mijpeterson
changed the title
shalinikhare27
previously approved these changes
Jun 5, 2024
emilyyang-ms
previously approved these changes
Jun 5, 2024
mijpeterson
dismissed stale reviews from emilyyang-ms and shalinikhare27
via
c4ea270
emilyyang-ms
approved these changes
Jun 6, 2024
Haard30
approved these changes
Jun 6, 2024
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.
The secure future initiative is making it increasingly difficult to continue supporting the build and release of "production" tools via GitHub Actions/Workflows. This appears to be because of the fact that GitHub itself is considered an untrusted "environment", especially from the perspective of our production tenants.
This official Microsoft Open Source doc explains those considerations in detail and are a good signal for us to move to Azure Pipelines.
This PR will be the first in a series designed to move us away from GitHub workflows to Azure Pipelines. It introduces a new pipeline that will live side-by-side with our existing workflow. This new pipeline will act as a testing ground for us, in which we'll iteratively port over steps from our workflow.
Unfortunately, as there is no way to test out these pipelines on a GitHub connected repo until they're merged into main, there will likely be many PRs introducing experimental changes to the pipeline.