Build job does not work without SSHFS credentials
The plan was that the build job would be able to optionally use SSHFS to include existing parent commits for a better commit history. This does not seem to work yet.
In this instance I have to notice that it might not even be desired to implicitly allow SSHFS to be optional because in a production environment you might want the build job to fail if it cannot start off the production HEAD. So I think while it should be possible in theory to build without an SSHFS remote available I'm not yet sure on how to build it such that:
- merge-request pipelines, especially unprotected ones and those from forks, will be able to run (only yield and delta should be excluded from those)
- production pipelines on protected branches can enforce SSHFS on a job
Maybe it's as simple as if no creds are provided, run the job anyway (fallback), but if creds are provided and the mount fails also fail the entire job. That would make sense I guess.