Apply postprocessing to avoid any downtime in new documentation environments
The following discussion from !38 (merged) should be addressed:
-
@blsqr started a discussion: (+6 comments)
… I see a little problem with this line (and the lack of the
postprocess.sh
script): It leads to the documentation being offline until the new version is uploaded – which could take quite some time.To assure uniqueness, I'd propose to still push the documentation named by their
CI_COMMIT_SHORT_SHA
, but then let the post-processing script take care of renaming, linking, deleting... Should not be too hard. What do you think? -
If everything is fine, yep, this should not take too long, uploading 40 MB over direct network connection; however, if the connection or the copy operation fails for any reason, no documentation is available.
The safest way, in my mind, would be:
- Store documentations in folders named after the short SHA
- For each branch, create a symlink that points to the latest commit directory
- Regularly delete those commits that are no longer linked to
There is still stuff that can go wrong... but less than in the copy operation...? You know what I'm getting at?