Separate PR and Signed pipelines, migrate to 1ES pipelines templates #16821
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
✅ No release notes required |
vzarytovskii
commented
Mar 6, 2024
vzarytovskii
commented
Mar 11, 2024
T-Gro
approved these changes
Mar 12, 2024
psfinaki
reviewed
Mar 13, 2024
psfinaki
reviewed
Mar 13, 2024
psfinaki
reviewed
Mar 13, 2024
psfinaki
reviewed
Mar 13, 2024
psfinaki
approved these changes
Mar 14, 2024
KevinRansom
approved these changes
Mar 14, 2024
|
Caution Repository is on lockdown for maintenance, all merges are on hold. |
|
This one succeeds full cycle - PR builds, signed builds, insertion into SDK and into VS. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
We will now have two separate pipeline definitions:
azure-pipelines.ymlfor official signed builds, it will use standard 1ES template, with additional injected checks. This pipeline will build packages, publish them to darc, and trigger VS insertion (only for release branches). It only runs on pushes to branches in the signed pipeline.azure-pipelines-PR.ymlfor PR builds, this will be running on each PR to main or release branch and run standard set of tests. It runs on both pushes and PRs in public pipeline.On the higher level nothing should change, other than we'll just have them separate as well as based off of 1ES pipeline templates.