Webhook not working when Repo Clone URL set to HTTP

mohamicorp / stash-jenkins-postreceive-webhook

Webhook used to notify Jenkins when commits are made to Stash

Other

138 stars 98 forks source link

Webhook not working when Repo Clone URL set to HTTP #151

Open henryechen opened 9 years ago

henryechen commented 9 years ago

I just found an issue where the webhook does not work when 'Repo Clone URL' is left as HTTP. I had to change the URL type to Custom and put in the same URL that was listed under HTTP to get builds on commit working.

omicloud commented 8 years ago

Tried that, but it always switches back to HTTP after saving the config. How did you do it?

henryechen commented 8 years ago

It always changes back for me too but still works.

On Nov 20, 2015, at 5:24 AM, omicloud notifications@github.com wrote:

Tried that, but it always switches back to HTTP after saving the config. How did you do it?

— Reply to this email directly or view it on GitHub.

psykx commented 8 years ago

I can confirm the following behaviour:

set to HTTP/SSH the post commit hook does not trigger a build
set to custom with the same URL as HTTP/SSH the post commit hook works
After saving a custom URL and reopening the settings menu, custom is no longer selected. In case changes need to be saved custom must be reselected to not brake the hook.

njtman commented 8 years ago

Any update on this one? I am see the same problem, except setting the custom field doesn't fix the problem for me!

Pressing the trigger build button in a pull request or inside of the post-commit webhook settings for the plugin does successfully trigger a build.

A build doesn't fire off when checking code into a repo however.

herebebogans commented 8 years ago

I have the exact opposite problem - HTTP works fine as the webhook URL ,but SSH doesnt.

Jenkins returns a "No git jobs using repository: ssh:// and the pipeline job has SCM enabled etc.

herebebogans commented 8 years ago

OK Not sure if we had the exact same issue but we managed to solve it by doing a manual build in Jenkins after changing the clone URL. This somehow updates the webhook to match up the SCM poll URL.

thrownullpointer commented 7 years ago

The jenkins job config xml isn't actually updated until you trigger your next job. I think your job was just out of synch...