Proposed: Zip .NET in-proc perf tests to allow for automated perf tests #2694
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
…e-extension into dajusto/zip-perf-tests
davidmrdavid
changed the title
bachuv
approved these changes
Dec 12, 2023
Co-authored-by: Varshitha Bachu <[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.
Please see the internal thread on this PR for more context
This PR adds two steps to our release pipeline:
(1) It creates a zip-deployable payload of our .NET in-proc perf tests
(2) It moves that .zip to the directory where our ADO publishing payload is located.
With these two changes, ADO should be able to pick up our .NET in-proc perf tests and consume them in an automated performance testing runner. Doing this should reduce the friction in our release process.