|
|
|
[
Permlink
| « Hide
]
Irina Kotlova [02/Jul/14 09:52 PM]
This is the script that gets executed.
The substitution started at 4:46 PM, ended at 05:04 PM. This is way too long time. (I added additional logging to the script.) In comparison Unix runs for 4 seconds.
I guess this might be caused by some environmental issues. Please run the agent (or server) running this step in console mode by stopping it and issuing "bin/agent.bat console" (or "bin/server.bat console" if it is a server) from the same command prompt where the batch file runs fast. Then run the batch in QB again to see what happens.
Oops - always forget to try console mode. It is because I was not expecting QuickBuild doing something wrong :-) was assuming anti-virus is a player here or something else.
So, in console mode the script got executed in just 6 seconds! Is there a way to fix this without switching to the console mode? Console mode is less secure and a bit more complex to maintain, because it requires to set up automatic service startup on reboot, it means that the build user password should be put in the registry, anybody unlocking the system immediately gets access to it. Thanks! The problem now is fixed: I switched to SourceForge's sed.exe from UnixUtils. Sorry for the hassle.
Normally it is an environmental issue if some things works normally if run from command line but not from QB. So running QB in console mode is to make sure that they use the same environments. In this case, the sed.exe from git might not work normally when calling from a background Windows service.
|