In this PR, I make a copy of the "Release Extension 2.x" pipeline that triggers nightlyiff there's any new code merged in dev. If we incorporate this pipeline, we should be able to create automation that runs e2e perf tests on the same night as new code is merged into the dev branch. That should help us catch performance regressions faster.
Additionally, this also paves the way for potentially created a nightly package on ADO, which may have its own servicing wins. That said, this PR is primarily for E2E testing automation.
This is a follow up to: https://github.com/Azure/azure-functions-durable-extension/pull/2694
In this PR, I make a copy of the "Release Extension 2.x" pipeline that triggers nightly iff there's any new code merged in
dev
. If we incorporate this pipeline, we should be able to create automation that runs e2e perf tests on the same night as new code is merged into thedev
branch. That should help us catch performance regressions faster.Additionally, this also paves the way for potentially created a nightly package on ADO, which may have its own servicing wins. That said, this PR is primarily for E2E testing automation.