Emmanuele Bassi commented:
@averi The "let's use a VM" was a stand-in for "let's use something that retains state instead of a container that gets torn down every time"; an OpenShift container running httpd is absolutely fine, as long as the container retains state when it's terminated. I guess it could be backed up somewhere, so if it gets re-spun, the built API reference are still available.
There's also the option of pushing build artefacts to some S3 bucket from a tagged, ad hoc CI runer, and then have another container serve data from that S3 bucket, if it makes administering this kind of set up easier.