Pipeline jobs might (probably) invoke an sh step.
Such step are including a shebang on the underlying script.
Such shebang caused the script to be mode changed to executable.
These "executables", when written on a mounted filesystem with the noexec flag, become non-executable, causing a not obvious failure (in fact, no error is shown beyond a non executing step).
Replacing the bare executable script with a call to the runner defined at the shebang, avoids this situation