Wouldn't have thought so but sounds like its all fixed for now so all good
now I guess :)
Richard.
On Tue, Jun 25, 2013 at 11:54 PM, Jon Schewe wrote:
> I just reconfigured my Jenkins to be behind apache so that it's on port 80
> and SourceForge will let me hit it and now the nofityCommit hook
I just reconfigured my Jenkins to be behind apache so that it's on port 80
and SourceForge will let me hit it and now the nofityCommit hook works.
Perhaps something about being exposed on an alternate port?
On Tue, Jun 25, 2013 at 5:44 AM, Jon Schewe wrote:
> Here's what I get:
>
> >curl
> http
Here's what I get:
>curl
http://mtu.net:8042/jenkins/git/notifyCommit?url=http://git.code.sf.net/p/fll-sw/code
Error 404Status Code: 404Exception: Stacktrace:
(none)
Generated by Winstone Servlet Engine
v0.9.10 at Tue Jun 25 06:43:36 EDT 2013
On Mon, Jun 24, 2013 at 9:35 PM, Richard Bywater wro
You might want to post the stack trace as it should just work. From the
blogpost: "Finally, this URL doesn’t require authentication even for
secured Jenkins, because the server doesn’t directly use anything that the
client is sending."
That's the behaviour that I have working in the instance I run
I see instructions at [1] for how one should be able to trigger a build.
However I have a secured Jenkins and visiting the URL on my site results in
a stack trace unless I'm logged in. Do I need to give anonymous some
permissions? I'm using project based matrix authorization and anonymous has
read
