Create a unittest pipeline, moving common steps into templates, disable CosmosDB testing on linux #2049
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
Aniruddh25
requested review from
JelteF,
Mathos1432,
aaronburtle,
aaronpowell,
abhishekkumams,
ayush3797,
gledis69,
mbhaskar,
milismsft,
ravishetye,
seantleonard,
severussundar and
tarazou9
as code owners
Collaborator
Author
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
abhishekkumams
approved these changes
Feb 19, 2024
ayush3797
approved these changes
Feb 19, 2024
seantleonard
pushed a commit
that referenced
this pull request
Mar 2, 2024
…le CosmosDB testing on linux (#2049) ## Why make this change? - Trying to improve the pipeline triggering experience by moving all PR validation pipelines to public project. - Desired goal is to have all pipelines automatically trigger upon commenting `/azp run` on an approved PR by a team member ## What is this change? - Create a unittest pipeline to run unittests - Move common steps and variables from original build pipeline to templates - Remove testing on the linux platform for CosmosDB in preparation to run this pipeline in the public project too. Its been difficult to start a CosmosDB emulator on linux, preventing us to test on this platform in the public project where pipeline secrets aren't allowed for PRs from forked repositories. (they are allowed in private projects, hence we had been able to test on linux when the pipeline was in the private project) ## How was this tested? - Temporarily renamed the unittest-pipelines.yml as build-pipelines.yml and ran the `Build` pipeline on this branch to verify a successful build 
seantleonard
added a commit
that referenced
this pull request
Mar 3, 2024
…plates, disab… (#2070) …le CosmosDB testing on linux (#2049) ## Why make this change? - Trying to improve the pipeline triggering experience by moving all PR validation pipelines to public project. - Desired goal is to have all pipelines automatically trigger upon commenting `/azp run` on an approved PR by a team member ## What is this change? - Create a unittest pipeline to run unittests - Move common steps and variables from original build pipeline to templates - Remove testing on the linux platform for CosmosDB in preparation to run this pipeline in the public project too. Its been difficult to start a CosmosDB emulator on linux, preventing us to test on this platform in the public project where pipeline secrets aren't allowed for PRs from forked repositories. (they are allowed in private projects, hence we had been able to test on linux when the pipeline was in the private project) ## How was this tested? - Temporarily renamed the unittest-pipelines.yml as build-pipelines.yml and ran the `Build` pipeline on this branch to verify a successful build  Co-authored-by: Aniruddh Munde <[email protected]>
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.
Why make this change?
/azp runon an approved PR by a team memberWhat is this change?
How was this tested?
Buildpipeline on this branch to verify a successful build