Why are merge requests triggered by Jenkins Cron?

[z00dev]

In gitlab there is a webhook to start the merge request builder in Jenkins, but in the configuration there is a cron configuration, Jobs are triggered by the Cron it seems, how would i configure it so the webhook starts the job instantly?

Plugin Version: 2.0.0
Jenkins Version: 1.642.2
Gitlab CE Version: 8.5.4

[marrrschine]

same question here!

[hoopesj]

+1 !

[jwg4]

I believe that the webhook WILL start the job instantly. The cron settings just give you another way of triggering the same job.

[marrrschine]

why did you close the issue? what is the solution? the build jobs will not be triggered unless you configure a cron job.

[timols]

@marrrschine I assumed that @jwg4's answer was sufficient:

I believe that the webhook WILL start the job instantly. The cron settings just give you another way of triggering the same job.

[marrrschine]

but it's not. automatic trigger does not work.

[timols]

@marrrschine would you be interested in submitting a PR to resolve this issue?

[jwg4]

Correct me if I'm wrong, I think that @marrschine's issue is a little different from the original issue. They are saying that if you don't have cron triggers configured, webhooks don't work at all. But if you do have cron triggers, the job can be successfully triggered by a webhook (without waiting for the next poll). I think this might be the case based on my experience.