fred rosenberger wrote:your first step should always be the logging - assuming there is any. if not, can you add some? a few simple echo statements should help you figure out where it is hanging...
has the script changed recently (i.e about two months ago)? Has anything the script does/calls/talks to/looks at changed? You need to figure out where to focus your investigation, and the logging is your best bet.
If you can't look at or add any, then try and figure out how far the script does get...it always frustrated me that we never had a shell debugging too...but sometimes you can even run the commands manually, one at a time, to figure out what might be hanging...but that depends on what exactly each command does...
Jeanne Boyarsky wrote:Pankaj,
O'Reilly has a good book on Jenkins, but it is old and some things have changed.
There's also the official docs which are good but a little dry.
I skimmed this tutorial and it looks good.