Thanks, Joan. Unfortunately, that doesn't seem to be the problem. Switching things from git:// back to https:// produces the same result:
https://builds.apache.org/view/E-G/view/Guacamole/job/guacamole-server-pull-request/13/console The Jenkins build cited in the documentation as an example ( https://builds.apache.org/job/dir-scimple-pull-requests/) also uses git:// (though appears to have not run in 4 months). - Mike On Tue, Jun 9, 2020 at 5:15 PM Joan Touzet <woh...@apache.org> wrote: > Try specifying your git repository as > https://github.com/apache/guacamole-server instead of > git://github.com/apache/guacamole-server.git ? Just a guess. > > On 09/06/2020 16:45, Mike Jumper wrote: > > Hello all, > > > > I've been trying to configure Jenkins jobs to automatically build pull > > requests for the Guacamole repositories on GitHub using the "CloudBees > Pull > > Request Builder" as documented here: > > > > > https://cwiki.apache.org/confluence/display/INFRA/Kicking+off+a+build+in+Jenkins+with+a+GitHub+PR > > > > > https://docs.cloudbees.com/docs/admin-resources/latest/plugins/pull-request-builder-for-github > > > > So far, I am having no luck, with the current attempt producing a cryptic > > IOException apparently related to git: > > > > "... hudson.remoting.ProxyException: > > hudson.remoting.FastPipedInputStream$ClosedBy: The pipe was closed at... > > at > > hudson.remoting.FastPipedInputStream.close(FastPipedInputStream.java:112) > > at org.apache.commons.io.IOUtils.closeQuietly(IOUtils.java:363) > > at org.apache.commons.io.IOUtils.closeQuietly(IOUtils.java:284) > > at > > > com.cloudbees.jenkins.plugins.git.vmerge.ChannelTransport$GitPushTask.invoke(ChannelTransport.java:133) > > at > > > com.cloudbees.jenkins.plugins.git.vmerge.ChannelTransport$GitPushTask.invoke(ChannelTransport.java:117) > > at hudson.FilePath$FileCallableWrapper.call(FilePath.java:3052) > > at hudson.remoting.UserRequest.perform(UserRequest.java:212) > > at hudson.remoting.UserRequest.perform(UserRequest.java:54) > > at hudson.remoting.Request$2.run(Request.java:369) > > Caused: hudson.remoting.ProxyException: java.io.IOException: Pipe is > > already closed > > at > > > hudson.remoting.FastPipedOutputStream.write(FastPipedOutputStream.java:154) > > at > > > hudson.remoting.FastPipedOutputStream.write(FastPipedOutputStream.java:138) > > at > > hudson.remoting.ProxyOutputStream$Chunk$1.run(ProxyOutputStream.java:255) > > at hudson.remoting.PipeWriter$1.run(PipeWriter.java:158) > > at > > java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > > at > > > hudson.remoting.SingleLaneExecutorService$1.run(SingleLaneExecutorService.java:131) > > at > > > hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72) > > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > > at > > > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) > > at > > > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) > > at java.lang.Thread.run(Thread.java:748) > > Caused: java.io.IOException: Pipe is already closed > > ..." > > > > (see > > > https://builds.apache.org/view/E-G/view/Guacamole/job/guacamole-server-pull-request/12/console > > ) > > > > Any ideas on what might be going wrong here, or any examples on this > being > > used in practice? > > > > Thanks, > > > > - Mike > > >
