Migrate ADO Release to 1ES ADO Pipeline #1461
Merged
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
WardenGnaw
requested review from
mpeyrotc,
chuckries,
asundheim and
gregg-miskelly
gregg-miskelly
approved these changes
Aug 28, 2024
WardenGnaw
force-pushed
the
dev/waan/addReleasePipeline
branch
from
b654fd0
to
c9d01ce
Compare
|
@gregg-miskelly I've discussed with Austen about how we should do this for all the repos. After discussing, it would be preferable that we do the insertion as part of the official build since if it's in its own stage, it's easier to just requeue that if it fails. |
gregg-miskelly
approved these changes
Aug 30, 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.
This PR address the issue that ADO Release is not using a governed template. This PR adds the release stage as part of the official build