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

Gitlab Notifier not firing

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Component/s: gitlab-hook-plugin
    • Labels:
      None
    • Environment:
      Gitlab Hook Plugin 1.4.0
      GitLab 7.14.1 481c966
      Jenkins 1.609.3
    • Similar Issues:

      Description

      When the build finishes, I am seeing no indication of notifications. I see nothing in the jenkins logs to indicate that a notification was attempted, nor do i see any indication of success/failure of any notifications. Neither to I see anything on the gitlab side to indicate a notification was attempted.

      Gitlab URL: http:mydomain.com
      Gitlab token: validtoken
      Send notification as commit statuses: unticked
      Only submit status for merge projects: unticked

      As an exercise, I tried both "http:mydomain.com" and "http:mydomain.com/api/v3". The code looks like it doesn't want the "api/v3", but the help for the field says it does. I have also fiddle with the tick boxes to check if any different combination would make anything work. The user for the token is a reporter on the project and I have verified that the token is valid.

      Googling didn't lean to any help, I'm guessing this isn't a problem with the code because no one else is talking about it, but I can't see what i messed up in the configuration.

        Attachments

          Activity

          Hide
          javiplx Javier Palacios added a comment -

          The 'api/v3' has been removed from documentation. But you are right that there is no clear indication on the job log for the notifier. At the very end of the log you might see a message like

          [workspace] $ git log -1 --oneline --format=%P
          

          but it only serve to check that it was fired (I'll add some real feedback for the posting result). I believe that the important point is that reporter permission could not be enough, as the user must be capable of adding comments to a commit (see this for example). If you increase the privileges of the user, it will probably work.
          But with standard gitlab this feature is on my believe more useful for reporting to merge requests, and maybe there reporter permission could suffice.

          Show
          javiplx Javier Palacios added a comment - The 'api/v3' has been removed from documentation. But you are right that there is no clear indication on the job log for the notifier. At the very end of the log you might see a message like [workspace] $ git log -1 --oneline --format=%P but it only serve to check that it was fired (I'll add some real feedback for the posting result). I believe that the important point is that reporter permission could not be enough, as the user must be capable of adding comments to a commit ( see this for example ). If you increase the privileges of the user, it will probably work. But with standard gitlab this feature is on my believe more useful for reporting to merge requests, and maybe there reporter permission could suffice.
          Hide
          javiplx Javier Palacios added a comment -

          The latest snapshot gives feedback on the job console as well as in the jenkins logfile. In particular, it should give the message returned by gitlab if the operation is not successful.
          That snapshot also has basic support of commit status API available since gitlab 8.1, which might be interesting accounting for the kind of things you were trying to do with the plugin.

          Show
          javiplx Javier Palacios added a comment - The latest snapshot gives feedback on the job console as well as in the jenkins logfile. In particular, it should give the message returned by gitlab if the operation is not successful. That snapshot also has basic support of commit status API available since gitlab 8.1, which might be interesting accounting for the kind of things you were trying to do with the plugin.

            People

            • Assignee:
              javiplx Javier Palacios
              Reporter:
              phillipgreenii Phillip Green
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: