Friday 15 January 2010

build - How to make Cygwin the default shell for Jenkins? -


I'm trying to come up with some smart solutions for a written build using SCONS, which Depending on the applications, to access the paths like Unix, using paths like Unix. However, when I'm trying to use the Ascans plugin or GIT plugin in Jenkins, then it will somehow cmd / c Git.exe - and it will definitely fail, because Git Sigwin And was known only in the Saigwin shell, but not in CMD. But even if I can make GIT and the rest are available for CMD.XA, then other problems arise: the Sagvivin version of the GIT expects a forward slash and the backward slash to escape In form Kickback issues related to the idiotic Windows file system (I can not allow Jenkins to delete my own files!).

So, Jenkins is the only way to use the signin shell, and never cmd.exe? Or should I be prepared to run some Linux in VM so that it is handled?

You can configure Jenkins to perform the sync command with a specific shell command as follows:

  c: \ cygwin \ bin \ minutely --hold always --exec / cygdrive / c / path / to / bash / Script.sh   

Where script.sh Jenkins will execute all the commands required for execution.

No comments:

Post a Comment