Split the pipeline up on release builds#3247
Merged
mattleibow merged 26 commits intomainfrom Apr 24, 2025
Merged
Conversation
mattleibow
added a commit
that referenced
this pull request
Apr 25, 2025
* Split the pipeline up on release builds (#3247) * [azure-pipelines-native] Add CI triggers for primary branches (#3248) * [azure-pipelines-native] Add CI triggers for primary branches * Remove dev branches from CI trigger * Update azure-pipelines-native.yml --------- Co-authored-by: Matthew Leibowitz <mattleibow@live.com> * Add a cron job to make sure all is well (#3249) --------- Co-authored-by: Peter Collins <pecolli@microsoft.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description of Change
With all the scripts and steps added internally for security, compliance and product tracing, the yaml just got too big.
This PR splits out the various stages into templates, and then depending on the actual pipeline being run it will either be the Native -> Package -> Tests pipeline (release builds), or the complete pipeline (public builds).