On Mon, Sep 11, 2023 at 03:43:05PM +0200, Erik Skultety wrote: > This would normally be not needed at all, but the problem here is the > Shell-in-YAML which GitLab interprets. It outputs every command that > appears as a line in the 'script' segment in a color-coded fashion for > easy identification of problems. Well, that useful feature is lost when > there's indirection and one script calls into another in which case it > would only output the respective script name which would make failure > investigation harder. This simple helper tackles that by echoing the > command to be run by any script/function with a color escape sequence > so that we don't lose track of the *actual* shell commands being run as > part of the GitLab job pipelines. An example of what the output then > might look like: > [RUN COMMAND]: 'meson compile -C build install-web' > > Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx> > Erik Skultety <eskultet@xxxxxxxxxx>: > --- > ci/build.sh | 5 +++++ > 1 file changed, 5 insertions(+) Reviewed-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> With regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
