Define a development procedure
It might be useful if we define a development/testing procedure for the code that lives in this repo.
This should keep any change in this repo from potentially messing up all nightly throughput tests.
From the top of my head I'd say the simplest procedure might be to have two folders on the throughput machine:
- One folder that contains this repo checked out at a certain "release" tag (or master?) which runs all the standard nightly throughput tests.
- A second folder with a branch which is checked out to represent the bleeding edge from which we can run a couple of test throughput scenarios to confirm new changes work as expected.
Just brainstorming a bit, hoping for more input :)
cc @rmatev @maszyman