In the referenced issue, we have duplicated logic to fetch the previous workspace build and provisioner job and insert another provisioner job / workspace build using the same parameters etc. as the previous build.

I wouldn't be opposed to exposing a function like: database.CreateWorkspaceBuild. I'm not a massive fan either, because it certainly conflicts with database.InsertWorkspaceBuild. 🤷

Originally posted by @kylecarbs in #1183 (comment)

When we have another (third) valid use-case for this, extract a helper function to streamline creating a new workspace build.