Thanks Stephen. Sure that's the goal, however, I run Jenkins locally on my laptop by now, so I can't configure my git server to send notifications to a specific ip. I wanted to try polling until I install Jenkins to our server.
So I keep wondering why polling does not re-trigger the scan. On 18 Apr 2017 7:31 p.m., "Stephen Connolly" < [email protected]> wrote: Your aim should be to set it to 8h or daily and have push notification trigger builds. On Tue 18 Apr 2017 at 16:38, Ferran Pujol Camins < [email protected]> wrote: > Hello, > > I've setup a Multibranch Pipeline that works correctly when manually > launched with *Scan Multibranch Pipeline Now*. > > I have checked the *Periodically if otherwise not run* checkbox under *Scan > Multibranch Pipeline Triggers *and set the interval to 1 minute. However, > nothing happens. The scan is not re-triggered even though I have made > commits and created new branches. > > Also, there's nothing logged in *Multibranch Pipeline Events.* > > Is this a bug? Is there something I am missing? > > Best regards, Ferran. > > El dissabte, 11 març de 2017 3:55:49 UTC+1, Christopher Orr va escriure: > >> On Thu, 9 Mar 2017, at 15:53, Travis Camechis wrote: >> > Hey guys, >> > >> > I have a multibranch pipeline defined but it will not poll. It is set >> up >> > like such >> > >> > node { >> > >> > git poll: true, url: 'ssh://.........' >> > >> > stage("build") { >> > checkout scm >> > } >> > >> > >> > Any suggestions on why this would not poll ? Also how do you tell it >> how >> > often ? >> >> You should preferably be using Git webhooks to tell Jenkins when there >> has been a change: >> https://plugins.jenkins.io/git#GitPlugin-Pushnotificationfromrepository >> >> But you can additionally tell Jenkins to regularly re-scan the >> repository for new branches, by using the "periodically if not otherwise >> run" option: >> https://jenkins.io/doc/book/pipeline/multibranch/#creating-a-multibranch- >> pipeline >> >> Regards, >> Chris >> > -- > 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]. > > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-users/ebd80000-0ac1-4835-815a-90219ffa78ea%40googlegroups. > com > <https://groups.google.com/d/msgid/jenkinsci-users/ebd80000-0ac1-4835-815a-90219ffa78ea%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Sent from my phone -- You received this message because you are subscribed to a topic in the Google Groups "Jenkins Users" group. To unsubscribe from this topic, visit https://groups.google.com/d/ topic/jenkinsci-users/dKpRv-UY9BM/unsubscribe. To unsubscribe from this group and all its topics, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/ msgid/jenkinsci-users/CA%2BnPnMzJAyzm%3DrT55T%3DFRx__ FEzz24JszXTGmoPsTZiA1c2dbQ%40mail.gmail.com <https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMzJAyzm%3DrT55T%3DFRx__FEzz24JszXTGmoPsTZiA1c2dbQ%40mail.gmail.com?utm_medium=email&utm_source=footer> . For more options, visit https://groups.google.com/d/optout. -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/CAP9NH%3DFMADhj6Nh%2B4B02C4mSVj36qhi%3D8Q%2BpyMaOxbH8wL7wXQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
