set -x is the default but it's not ideal.
When you have pipes and redirections it's hard to tell what's going on.
A better solution would be to do something like
cp $BASH_SOURCE /tmp/Jenkins/scripts
To copy the currently executing script to some folder of your choosing (you
could use mktemp but
Thanks Daniel.
Nick.
On Friday, September 12, 2014 2:05:17 PM UTC-7, Nick Dierauf wrote:
Hello,
I am getting the following error while attempting to execute my Jenkins (v
1.577) job:
[workspace] $
If this is a freestyle job, you could add set -x before the first build
step and it'll output all executed shell commands.
Regards,
Daniel Serodio
On Thursday, October 2, 2014 6:50:50 PM UTC-3, Nick Dierauf wrote:
Would love to get some insight into this temporary file that Jenkins
creates.
Would love to get some insight into this temporary file that Jenkins
creates. Anybody care to respond? Thanks!
On Fri, Sep 12, 2014 at 2:05 PM, Nick Dierauf ndier...@gmail.com wrote:
Hello,
I am getting the following error while attempting to execute my Jenkins (v
1.577) job:
[workspace] $
Hello,
I am getting the following error while attempting to execute my Jenkins (v
1.577) job:
[workspace] $
/home/administrator/Hudson/instances/Albatross/tomcat-8092-8022/temp/hudson8884100134029098059.js
FATAL: command execution failedjava.io.IOException
