-
Notifications
You must be signed in to change notification settings - Fork 619
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent failures to trigger a Jenkins build when an MR first opened #250
Comments
Actually, seems a bit worse than what's above. I've just opened an MR to find the exception thrown in the logs and no build triggered, but then closing/re-opening the MR doesn't trigger it either - the same exception is thrown. I then trimmed down the webhooks on the Gitlab project so that there was just a single one left, but the same thing seems to happen. |
Apologies for the stream of consciousness on this, but it seems to be happening across projects now - we're not getting any triggering. The version of Gitlab hasn't changed since it was all working well, but we have upgraded Jenkins (and, perhaps, dependent, plugins). We're currently running Jenkins 1.655, so the issue definitely occurs with 1.654 and 1.655. Again, don't know if it's related, but |
I looked into this and was about to comment to say I have no idea what is going on, but it looks like @pbendersky does :) We will review his PR. |
Ah - interesting (and thanks for looking). Will keep an eye on the PR. For the existing case, it seems to happen all the time for us now, but only with MR events - we always get the exception and no triggered build. This did all work previously, and work really well, so I'm suspecting a Jenkins/dependent Jenkins Plugin might be the cause? When making a push to the source branch of an MR, after opening and the initial failure, a build does always seem to be triggered - in the logs |
@cotman I would suggest you try upgrading to the latest version of the plugin, it has a substantial refactor of code and may resolve this issue on its own. Let me know if not. |
Hi,
I've noticed comments in other issues, elsewhere, but they seem to suggest they've gone away?
I'm running:
Jenkins: 1.654
Gitlab Plugin: 1.1.32
Gitlab: 8.5.4
For the most part, everything works brilliantly. However...occasionally when opening an MR, a build isn't triggered and I see the following in the
jenkins.log
:As above - it seems to work sometimes, but not others. When it doesn't work, providing another triggered event (MR related or pushing to the source branch in the MR) and the build gets triggered correctly.
I guess the empty
INFO: WebHook called with url:
is a little suspicious?The Gitlab projects I've seen this on have (so far) got 2 webhooks associated with them - don't know if that's related?
The Gitlab webhooks are configured to be executed on MR events and push events, and I have the following Gitlab Plugin options selected on the job:
Thanks.
The text was updated successfully, but these errors were encountered: