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.
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.