Bugzilla

(In reply to Armen [:armenzg] from comment #10)
 
> I was not asking to remove the jobdetails endpoint or to stop storing anything related to TinderboxPrints.
> My original request was not to store artifacts in the DB since it has a high write impact and we can instead list in the UI the artifacts from TC APIs or put a link to the TC UI that shows artifacts for a task.

Yes, I know. But instead of only focusing on one aspect - the storage of uploaded artifacts - I think it's worth evaluating whether or not we should be storing the TinderboxPrint data in the table and whether we need to have the /jobdetails/ endpoint at all. But like I said, that'll be a next step.

(In reply to Armen [:armenzg] from comment #10)
 
> I was not asking to remove the jobdetails endpoint or to stop storing anything related to TinderboxPrints.
> My original request was not to store artifacts in the DB since it has a high write impact and we can instead list in the UI the artifacts from TC APIs or put a link to the TC UI that shows artifacts for a task.

Yes, I know. But instead of only focusing on one aspect - the storage of uploaded artifacts - I think it's worth evaluating whether or not we should be storing the TinderboxPrint data in the table and whether we need to have the /jobdetails/ endpoint at all (I was a little premature in thinking we could do this right away, but now that I've done more research I still think it's worth considering). But like I said, that'll be a next step.