I observed this problem too, but at the end I discovered that the output
doesn't come
from the git hook, but from the jenkis log, because I started for test
reasons the
jenkinsserver in the same terminal in background :-(
Are you sure that jenkins has been started as a demon or at least
detache
On Mon, Jan 21, 2013 at 7:39 PM, Mark Waite wrote:
> With the version of curl I'm using (7.26.0 - as delivered with Debian
> "Wheezy"), I can use the arguments -o /dev/null to prevent that output.
> Does that not work for you?
The git server has curl-7.15.5 and I thought I'd already tried that
op
With the version of curl I'm using (7.26.0 - as delivered with Debian
"Wheezy"), I can use the arguments -o /dev/null to prevent that output. Does
that not work for you?
Mark Waite
>
> From: Adam Mercer
>To: jenkinsci-users@googlegroups.com
>Sent: Monday, Ja
On Mon, Jan 21, 2013 at 5:38 PM, Adam Mercer wrote:
> this seems to be working great, i.e. a new build is scheduled if
> appropriate. However the post-receive hook outputs:
>
> Scheduled polling of Project
An example is:
$ git push
Counting objects: 9, done.
Delta compression using up to 4 thre
