• 1.5.21

      After gitlab-plugin update (to 1.5.19, current is 1.5.13)  no push events are detected. In gitlab the return code is ok (200).

          [JENKINS-65041] Gitlab Webhooks Not Triggering builds

          Chisel added a comment -

          After updating the plugin on Friday afternoon we are also getting similar reports of the webhook not triggering builds. 

          Jenkins 2.282 /  gitlab-plugin 1.5.19 also.

          Chisel added a comment - After updating the plugin on Friday afternoon we are also getting similar reports of the webhook not triggering builds.  Jenkins 2.282 /  gitlab-plugin 1.5.19 also.

          Joschua Grube added a comment -

          Same issue here. We had to rollback to plugin version 1.5.13 which fixed this issue.
          Jenkins 2.263.4 (LTS) / GitLab 13.6.2

          Joschua Grube added a comment - Same issue here. We had to rollback to plugin version 1.5.13 which fixed this issue. Jenkins 2.263.4 (LTS) / GitLab 13.6.2

          Javier added a comment - - edited

          Same issue, same jenkins (2.263.4 (LTS)) and same solution: rollback gitlab plugin to 1.5.3.

          To provide a few more details:

          • Gitlab sends the webhook and receives 200
          • A manual GET with the webhook url (using browser, postman or curl) returns 404:
          • HTTP ERROR 404 Not Found

            URI: /jengis/project/<job-name>
            STATUS: 404
            MESSAGE: Not Found
            SERVLET: Stapler
          • Jenkins receives the webhook: the log entry  is: 2021-03-09 20:49:19.229+0000 [id=23] INFO c.d.g.webhook.GitLabWebHook#getDynamic: WebHook called with url: /jengis/project/<job-name>
          • I'm using a multibranch pipeline, that can be executed manually, but not triggered from the webhook

          Javier added a comment - - edited Same issue, same jenkins (2.263.4 (LTS)) and same solution: rollback gitlab plugin to 1.5.3. To provide a few more details: Gitlab sends the webhook and receives 200 A manual GET with the webhook url (using browser, postman or curl) returns 404: HTTP ERROR 404 Not Found URI: /jengis/project/<job-name> STATUS: 404 MESSAGE: Not Found SERVLET: Stapler Jenkins receives the webhook: the log entry  is: 2021-03-09 20:49:19.229+0000 [id=23] INFO c.d.g.webhook.GitLabWebHook#getDynamic: WebHook called with url: /jengis/project/<job-name> I'm using a multibranch pipeline, that can be executed manually, but not triggered from the webhook

          Oliver Grad added a comment -

          Same issue here.

          Jenkins 2.277.1 - gitlab-plugin 1.5.19

          Next would be to rollback the gitlab-pluing.

          At the moment all our development teams are blocked, as they use Multibranch-Pipelines intensivly.
          Is it possible to raise the priority?

          Oliver Grad added a comment - Same issue here. Jenkins 2.277.1 - gitlab-plugin 1.5.19 Next would be to rollback the gitlab-pluing. At the moment all our development teams are blocked, as they use Multibranch-Pipelines intensivly. Is it possible to raise the priority?

          Oliver Grad added a comment -

          additional information: downgrade of gitlab-plugin to version 1.5.13 helped to recover the functionality.

          Oliver Grad added a comment - additional information: downgrade of gitlab-plugin to version 1.5.13 helped to recover the functionality.

          Possibly fixed in v1.5.21: https://github.com/jenkinsci/gitlab-plugin/blob/master/CHANGELOG.md#1521 (not released yet though)

          Dmitry Erastov added a comment - Possibly fixed in v1.5.21: https://github.com/jenkinsci/gitlab-plugin/blob/master/CHANGELOG.md#1521 (not released yet though)

            jequals5 Marky Jackson
            claudiol Claudio Lezcano
            Votes:
            8 Vote for this issue
            Watchers:
            15 Start watching this issue

              Created:
              Updated:
              Resolved: