run_cmdline is not verbose enough
The run_cmdline
is not verbose enough.
On failure it currently just prints that the command failed with the error number.
That's not enough information because there might be lots of reasons for failure that are not conveyed by the number itself.
It should at least dump stderr to see what the command screamed about.
As example use case, the current beat/beat.nightlies> pipelines all fail on Linux since the introduction of !259 (merged).
I suspect that's because of the docker-build
tag that makes it use a shell gitlab-runner rather than the Docker executor and since the shell executor is run on a Debian machine, there's no reason for yum to be present.