search

pongasoft / glu

Deployment Automation Platform
Apache License 2.0
521 stars 99 forks source link

Find a way to display full output/error when forked process fails #293

Open ypujante opened 9 years ago

ypujante commented 9 years ago

As reported in this forum thread: http://glu.977617.n3.nabble.com/Glu-truncates-script-output-td4026892.html what happens is that ShellExec catches any error and throws an exception with an excerpt of the output and error (while preserving full output and error). There is currently no way to get a hold of the full output or error.

sodul commented 9 years ago

We have a similar issue. I think the current approach we (at Skyhigh Networks) should take is to catch the shell exec exception in the groovy script and have this print the tail of the python or whatever script (being called). I'm not sure it is desirable to modify the agent code to do that automatically modifying the default behavior of ShellExec. One option on the Glu Agent side could be to extend the ShellExec with a new option to throw the output of the called process with the current line number in the groovy script and the command line that was called. In that case capturing the output and present it to the stack trace is not necessarily trivial or desirable to implement directly in the agents either.