engineering: Modify azurelinux cicd template to suit automation#94
Closed
bfjelds wants to merge 2 commits into
Closed
engineering: Modify azurelinux cicd template to suit automation#94bfjelds wants to merge 2 commits into
bfjelds wants to merge 2 commits into
Conversation
0875a83 to
d9e23ee
Compare
f5f30fb to
4398b56
Compare
Member
Author
|
Replacing with #95 |
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
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
The azurelinux cicd pipeline should be triggered by pipelines owned by other teams, allow for BM tests to be disabled, and have junit artifacts that can be collected and published for each new azurelinux build.
📝 Checks