AnsweredAssumed Answered

Is cygwin considered an external interpreter for WINDOWS?

Question asked by RoddyJ on Nov 16, 2018
Latest reply on Nov 17, 2018 by RoddyJ

We currently use cygwin to execute shell (ksh) scripts on our windows agents.  For example, we insert something like this into our WIN JOBS object Process tab.  

 

c:\bin\cygwin\bin\mksh.exe -l -c "/home2/PROJECTCODE/bin/PROJECTCODE-JOBNAME.sh"
@set retcode=%errorlevel%
@if NOT %ERRORLEVEL% == 0 goto :retcode

 

But this limits us to executing those ksh scripts on the agent server, that is, we can't embed ksh scripts in our WIN JOBS objects.  At least we haven't found a way to do that.  Is there a way to setup cygwin as an external interpreter that will allow us to embed our ksh scripts in WIN JOBS objects?

 

I've reviewed this article: https://communities.ca.com/message/242146344-re-bash-under-window-agent?commentID=242146344#comment-242146344 

 

However, I don't think that applies to external interpreters, or, I may not understand exactly what external interpreters are intended for.

Outcomes