Custom tools get run in the background - output is not logged
Created originally on Bitbucket by DaveInCaz (David Hollman)
It looks like if you define a custom tool in workbench that is not an “hg…” or “thg…” command - ie just some other program, that program is always run without its output being captured and logged.
I think this originates here:
# Otherwise, run the selected command in the background try: res = subprocess.Popen(command, cwd=workingdir, shell=True)
This lack of feedback from the subprocess makes it kinda hard to debug a custom setup or any other output the user might need. In my recent case I’ve resorted to having the background process popup a GUI messagebox which is an OK workaround, but it would be much nicer for its stdout or stderr just to be captured & reported.