Are you looking for a temporary workaround? Make the trigger asynchronous. There are a number of ways to do this, but since I prefer python I would add a line in your post-commit hook to call a python script which spins off another process to trigger the Jenkins update.
http://stackoverflow.com/questions/1718899/run-a-process-and-quit-without-waiting-for-it You'll want to log the result somewhere since you won't get the return value from the async call in the post-commit script itself. -Kenny On Tuesday, April 30, 2013 1:39:09 PM UTC-7, Matt Seashore wrote: > > Fair enough. I've filed a bug here: > https://issues.jenkins-ci.org/browse/JENKINS-17808 > > On Tuesday, April 30, 2013 10:29:15 AM UTC-6, Jesse Glick wrote: >> >> On 04/29/2013 08:19 PM, Matt Seashore wrote: >> > is this a known issue >> >> If you have to ask, the answer is probably “no”. File it with whatever >> details to reproduce you can muster. >> > -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
