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

GitHub webhook is not created for new Pipeline

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Won't Fix
    • Labels:
      None
    • Environment:
      Jenkins 2.16
      GitHub API Plugin 1.76
      GitHub Branch Source Plugin 1.8.1
      GitHub Organization Folder Plugin 1.4
      GitHub plugin 1.20.0
      Pipeline 2.2
      Pipeline Multbranch 2.8
    • Similar Issues:

      Description

      GitHub webhook is not created when a new Multibranch Pipeline build is added.

      Jenkins has a GitHub server configured, with proper credentials and it's confirmed to be working in other scenarios. 'Auto-manage hooks' is configured.

      Tried to create a Multibranch Pipeline build in three different ways:

      • Specified GitHub project URL only (with proper credentials)
      • Specified Git repository URL only (with proper credentials)
      • Specified both GitHub project and Git repository (with proper credentials)

      In no case the GH webhook was created for the repository.

      Multibranch Pipeline Logs: None.

      Pipeline Logs:

      Aug 05, 2016 3:29:51 PM org.jenkinsci.plugins.github.webhook.WebhookManager$1 run
      INFO: GitHub webhooks activated for job repository-name-here with [] (events: [PUSH, REPOSITORY])
      

        Attachments

          Activity

          Hide
          gtirloni Giovanni Tirloni added a comment -

          Tested with simple Pipeline builds and it's the same issue. Updated ticket to reflect that.

          Show
          gtirloni Giovanni Tirloni added a comment - Tested with simple Pipeline builds and it's the same issue. Updated ticket to reflect that.
          Hide
          bascht Sebastian Schulze added a comment -

          I experienced the same issue (see comment in JENKINS-37216) and it fixed by running the first build manually like mentioned here: https://issues.jenkins-ci.org/browse/JENKINS-35132?focusedCommentId=260714&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-260714

          Show
          bascht Sebastian Schulze added a comment - I experienced the same issue (see comment in JENKINS-37216 ) and it fixed by running the first build manually like mentioned here: https://issues.jenkins-ci.org/browse/JENKINS-35132?focusedCommentId=260714&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-260714
          Hide
          lanwen Kirill Merkushev added a comment - - edited

          You should build first time the pipeline job manually to initialize git scm details by Jenkins. Github plugin gets the url of a project from the scm section, bit not from the property. When you use pipeline - scm section is not defined in job, but in pipeline script. So Jenkins should save this info after first build in programmatic way.

          It could be solved by using the property url to talk with Github, but it can brake some existing usecases... im still think how to implement it in safe way

          Show
          lanwen Kirill Merkushev added a comment - - edited You should build first time the pipeline job manually to initialize git scm details by Jenkins. Github plugin gets the url of a project from the scm section, bit not from the property. When you use pipeline - scm section is not defined in job, but in pipeline script. So Jenkins should save this info after first build in programmatic way. It could be solved by using the property url to talk with Github, but it can brake some existing usecases... im still think how to implement it in safe way

            People

            Assignee:
            lanwen Kirill Merkushev
            Reporter:
            gtirloni Giovanni Tirloni
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: