Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-73938

gitlab Webhook Comment and Job events are not working

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Blocker Blocker
    • gitlab-plugin
    • None

      Team ,

      We are facing the error when trigerring the gitlab webhook "comment" events , our gitlab is integrated with Jenkins version details are mentioned below . I already read the note related to this error => https://github.com/jenkinsci/gitlab-plugin/issues/1705, seems this plugin is for older jenkins version , Any update on jenkins version 2.462.3 , that we are running ? Can you please consider this ticket as priority ?

      Jenkins version => 2.462.3
      Gitlab API Plugin  => 5.6.0-97.v6603a_83f8690
      Gitlab Branch Source Plugin => 710.v6f19df32544b

      Please find the attached logs , also the error we are facing is : 

      Caught unhandled exception with ID f5ab8748-a053-41c5-9150-bfc0cf317052
      com.fasterxml.jackson.core.exc.InputCoercionException: Numeric value (2159427878) out of range of int (-2147483648 - 2147483647)

          [JENKINS-73938] gitlab Webhook Comment and Job events are not working

          Mark Waite added a comment - - edited

          balaganesh as far as I understand it, the issue was resolved in the GitLab plugin 1.9.4 release. You reported the version of GitLab branch source plugin but the stack trace in the log is from the GitLab plugin, not from the GitLab branch source plugin. Are you running the most recent release of the GitLab branch source plugin? If not, is the problem resolved when you upgrade the GitLab plugin to 1.9.4 or newer?

          Mark Waite added a comment - - edited balaganesh as far as I understand it, the issue was resolved in the GitLab plugin 1.9.4 release . You reported the version of GitLab branch source plugin but the stack trace in the log is from the GitLab plugin, not from the GitLab branch source plugin. Are you running the most recent release of the GitLab branch source plugin? If not, is the problem resolved when you upgrade the GitLab plugin to 1.9.4 or newer?

            baymac Parichay Barpanda
            balaganesh Balaganesh
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: