I found the following curl command to kill the slave and then Jenkins will automatically start it and I thought this might be a good workaround to get around git's lack of windows support but in testing I push to my repo and a build starts and succeeds, then the slave is killed and Jenkins restarts it, then I push to git again and the build tries to run but the workspace is now corrupt and nothing happens, then I push again and a build tries to occur but the pack file is locked.
curl -d "offlineMessage=&json=%7B%22offlineMessage%22%3A+%22%22%7D&Submit=Yes" http://[user]:[api token]@[host]/computer/[slave name]/doDisconnect Is anyone else successfully using windows and git? Will On 02/19/2013 07:52 AM, William Soula wrote: > I am trying to build a git project on a windows slave using Jenkins > 1.501 with git plugin 1.1.17. I like to wipe the workspace before > checking out so I have that option checked. When I run the build > sometimes it is able to delete the workspace but a lot of the time it > can't delete the workspace due to a pack file being locked. I checked > out what was locking the file and it is javaw.exe. If I restart the > slave then I am able to build once and then another pack file is locked > by the slave process. > > I have tried googling for a solution and apparently there is none > besides not using windows, which is not news to me, git is not a windows > tool, never supposed to be never will be. > > So my question is if there is some way to restart the slave within > another job. My idea is to have something like a the log analyzer > plugin detect the job failed due to the pack problem and kicks off > another job that kills the slave and restarts it and kicks off the first > job again. > > Will > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
