Long ago (before I ever started using Jenkins), there were cases where a shell script would pause for terminal input and would not work as a cron job, even though it worked correctly from a terminal. The issue (for me) was caused by some incorrect initialization commands (like `tset`) in one of my login defaults scripts (.profile, .kshrc, .bashrc, etc.). The defaults file was being sourced and was waiting for input from a terminal that did not exist (since it was running from cron).
I have not seen that problem in a very long time, so I'd be surprised if that is the problem, but you might double check just to be sure. Try running your script from a cron job or an "at" job to see if it behaves the same as when Jenkins runs it. Mark Waite >________________________________ > From: Eric L <ericl...@ericlong.com> >To: jenkinsci-users@googlegroups.com >Sent: Friday, March 15, 2013 9:14 AM >Subject: Automated perl scripts work fine in the terminal but hang when >Jenkins executes it. > > >I am running an automated perl DB upgrade script. > > >This script runs fine unattended in the terminal but hangs in Jenkins as if it >is waiting for a response. > > >Forgive me. I am very familiar with Jenkins and windows environments. I am >new to Linux (Ubuntu) environments. > > >Is it something related to how the shell is run under Jenkins compared to how >it is run from the terminal? > > >Any help would be greatly appreciated. > > >-Eric -- >You received this message because you are subscribed to the Google Groups >"Jenkins Users" group. >To unsubscribe from this group and stop receiving emails from it, send an >email to jenkinsci-users+unsubscr...@googlegroups.com. >For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
