It looks like it was an issue with defaulting to using C Shell. I don't entirely understand why this worked, but specifying to use Bash resolved the issues. This is what my Execute Shell prompt looks like now and it executes great.
#!/bin/sh -xe echo "Hello" > ~/tmp.txt Thanks for the help! Chris On Monday, June 18, 2012 3:34:02 PM UTC-6, slide wrote: > > Do you mean cat ~/tmp.txt? > > slide > > On Mon, Jun 18, 2012 at 2:23 PM, Chris Mitchell <mitchell....@gmail.com> > wrote: > > This is the Console Output for the Execute Shell of "echo ~/tmp.txt". > Is > > there any way to get more details about what exactly is going on? Any > > debugging output possibly? > > > > Started by user auser > > Building remotely on node in workspace > /u/auser/jenkins_bc/workspace/testing > > [testing] $ /bin/csh -xe /var/tmp/hudson118559907961626984.sh > > Finished: SUCCESS > > > > > > On Monday, June 18, 2012 3:08:06 PM UTC-6, Andrew Melo wrote: > >> > >> On Mon, Jun 18, 2012 at 4:05 PM, Chris Mitchell <mitchell....@gmail.com> > > >> wrote: > >> > I believe so. When I log in via SSH using the same account which has > >> > been > >> > configured for Jenkins and run the command, I get the desired output. > >> > >> Ah, but the environment for the slave is different than your > >> interactive environment. Try doing an echo ~/tmp.txt to see what the > >> shell is expanding it to > >> > >> > > >> > > >> > On Monday, June 18, 2012 2:42:09 PM UTC-6, LesMikesell wrote: > >> >> > >> >> On Mon, Jun 18, 2012 at 2:40 PM, Stanley, Jason > >> >> <jason.stan...@tekelec.com> wrote: > >> >> > Silly question. > >> >> > > >> >> > > >> >> > > >> >> > Are you looking on the correct node that ran the job for the > tmp.txt > >> >> > file? > >> >> > >> >> Also, are you sure you know how ~/tmp.txt will expand when run under > >> >> the jenkins slave? > >> >> > >> >> -- > >> >> Les Mikesell > >> >> lesmikes...@gmail.com > >> > >> > >> > >> -- > >> -- > >> Andrew Melo > > > > -- > Website: http://earl-of-code.com >
