On Wed, 05 Feb 2020 15:03:19 -0500 Randy Barlow bowlofeggs@fedoraproject.org wrote:
On Wed, 2020-02-05 at 11:47 -0800, Adam Williamson wrote:
We've kicked around the idea of an "execdb" before, I think...
Yeah, or it could just be a new table/API on resultsdb, to avoid complexities of starting and deploying a whole new project.
I'd push back on this pretty hard. Resultsdb is as useful as it is because it's so simple and "dumb". Adding features on top of what's already there starts to defeat that utility.
I'm personally of the mind that two small, simple services are easier to manage than one larger, more complex service.
Taskotron's execdb is a good example in my mind. Most of the dev/maintenance time that we ever put into that service was the frontend and how the data was presented to human users. That work would have to be done no matter where the backend functionality landed and keeping that functionality separate made it easier to maintain both codebases.
That being said, I have no real dog in this fight as someone else would end up doing the implementation.
The data would have a different schema than test results, which is why I advocate for at least giving it its own API and database table.
It sounds like we're of the same mind on this. I'm an advocate of keeping results and execution status separate because the primary audience/consumer for them are not looking for the same thing.
Anyhow, there may well be plans for something like this already. Hopefully someone will chime in if that's the case.
Tim