Monty Taylor
57229639e0
We're pushing artifacts to zuul on job completion, now we want to download those and upload them to the perf-tracker in promote. This is an abstract base job for doing that, so that we can provide per-project oidc secrets. We also want a periodic sweeper job to catch anything where the upload job didn't fire for whatever reason. Change-Id: I22864a59bcf21e55279fbedaa1de1a1fe16c8d87
Drizzle Tests
This is the Drizzle Test repository. It's where we keep tests of the Drizzle server.
Why, you might ask, in a separate repo rather than inside the Drizzle source itself?
A couple of reasons. One, we have a test runner in here which is in python and which is a different codebase than the C++ Drizzle source code. Second, we want to test the artifact that would run, the drizzle container image. We don't need the source code to do that.
Most importantly, c, if we've got agents running amok, it's good to put some friction in the way of behavior changes. Having tests and server in different places helps eversoslightly to mirror the real world where consumers have programs that use the server, and that don't change in lockstep with the server itself. So, if you have to think about how to roll out a change such that you don't break people, that's a good thing. And anything that helps gate the stream of agent commits is even better.
Also, fourth of all, we have Zuul and we can. :)