Closed
Description
Remote builds currently execute as if connecting to a session over SSH will always give a relatively sh
-style shell. This is not an assumption that should be made and should likely be solved by allowing the path to such a shell to be specified and assuming one exists at /bin/sh
(this latter point is up for debate).
The current behavior that is most likely to trigger this is that it attempts to execute if [ -f ~/.profile ]; then . ~/.profile; fi && cd {} && sh {}.sh
. This could also likely be addressed by giving users control over the script used to launch into the copied build script, but since build scripts basically assume sh
compatible shells exist anyway, this is probably not that useful.