jenkins - Execute shell waits before running -
i'm in process of migrating our build server local machine virtual 1 on ec2. i've got working, i've noticed when specify run in shell, hangs around 30 seconds or before running commands specified.
so example, first thing call env
print out environment variables aid troubleshooting:
if watch console output, line, followed spinner:
$ sh -xe c:\windows\temp\hudson8414496369434804156.sh
about 30 seconds later list of environment variables printed console.
during time spinner present without output, can navigate c:\windows\temp\
, open hudson8414496369434804156.sh
confirm file there contents of env
. can conclude it's not invoking shell while sat there...doing something.
this isn't 1 off, every time use execute shell
option under build
. next thing run git clone
command via execute shell
, , behaves same.
why taking long run shell commands, , how can stop this, or reduce waiting period?
i don't believe performance related issues machines, new 1 has better specification:
old machine: pentium dual-core e5400 2.7ghz
, 4gb ram
, 300gb hdd
, windows 8 pro
.
new machine: xeon e5-2670 v2 2.5ghz
, 4gb ram
, 300gb hdd
, windows server 2012 r2
.
the old version of jenkins didn't have issue 1.517
, , new version 1.613
. in system information
, java.runtime.version
1.7.0_21-b11
old, , 1.8.0_20-b26
new. going window's control panel, shows java 7 update 17 (x64) , java 8 update 45 (x64), respectively.
any ideas? google-fu has failed. cheers.
edit 1:
to answer slav's questions: running sh --version
in cmd
returns gnu bash, version 3.1.23(6)-release (i686-pc-msys) copyright (c) 2005 free software foundation, inc.
there's no delay.
creating dummy .sh
file in desktop folder, contents env
, , running in cmd
sh -xe dummy.sh
returns immediately, printing out environment variables.
Comments
Post a Comment