The Git repo URL that gets sent to Jenkins needs to be *just* the repo path; no query parameters, no branch names, nothing else. If it has extraneous stuff in it, it won't match the filters that are used to poke jobs, so it will be ignored.
----- Original Message ----- From: [email protected] To: [email protected] At: Jun 17 2013 15:02:43 >>> Are you letting the plugin create the webhooks or doing it manually? I am creating the web hook using this page: I have tried specifying the Jenkins URL to be things like: http://jenkins.netjets.com/jenkins I tried specifying the Git repo URL using things like: http://stash.netjets.com/scm/tes/frm4.git&branches=develop Thanks, Bob -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of William Soula Sent: Monday, June 17, 2013 1:53 PM To: [email protected] Subject: Re: Jenkins and Stash - Polling must die Are you letting the plugin create the webhooks or doing it manually? We haven't figured out how to have it create them automatically yet so we have to manually create the webhook in the github enterprise settings for the repo. Also, make sure you are pushing to the same branch that is being monitored, I believe that is taken into affect. What else have you tried? Will On 06/17/13 11:56, Bob Bick wrote: > Hi, > > I read Kohsuke's document on how polling should die: > > http://kohsuke.org/2011/12/01/polling-must-die-triggering-jenkins-builds-from-a-git-hook/ > > So, I decided to try to trigger Jenkins builds using a GIT hook: > > http://nerdwin15.com/2013/04/continuous-integration-with-stash-and-jenkins/ > > However, when I push code to the Stash repository, nothing happens (no build, > nada)... > > Q. Has anyone got Git hooks to work with Stash and Enterprise Jenkins? Any > ideas how to debug this type of issue (I do not see anything in any log file)? > > Our configuration: > Stash Enterprise from Atlassian v2.4.2 > Enterprise Jenkins ver. 1.466.12.1 from CloudBees > > Thanks in advance, > > Bob > > *** *** *** > This message contains information which may be confidential and privileged. > Unless you are the addressee (or authorized to receive for the addressee), > you may not use, copy or disclose to anyone the message or any information > contained in the message. If you have received the message in error, please > advise the sender by reply e-mail and delete the message. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. *** *** *** This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message.-- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out. -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
