It would be great to have an option to output the executed commands into the job build console for debugging purposes. right now only STDOUT and STDERR are logged.

for example i have a managed script like

BUNDLE_NAME=$(/usr/libexec/PlistBuddy -c "Print CFBundleDisplayName" ${WORKSPACE}/${1})

i call the managed script with the path to a plist as first argument with heavy usage of variables.

the only output in the build console i get is

Print: Entry, "CFBundleDisplayName", Does Not Exist

it would be nice to have something like in the "normal" build step script execution like:

++ /usr/libexec/PlistBuddy -c 'Print CFBundleDisplayName' /the/path/to/the/plist/as/defined/by/argument.plist
Print: Entry, "CFBundleDisplayName", Does Not Exist

of course i can add some variable dumps, but this seems very tedious as this works very nicely in the normal "execute script" build step.