[JIRA] (JENKINS-59876) Github orgnization commit trigger to build pipeline is not working through scm polling

[babu.kishore26@gmail.com (JIRA)]

Kishore Babu Kavuru created an issue

Jenkins / JENKINS-59876 Github orgnization commit trigger to build pipeline is not working through scm polling Issue Type: Bug Assignee: Mark Waite Components: git-plugin, github-api-plugin Created: 2019-10-22 05:29 Environment: windows jenkins 2.190 Priority: Critical Reporter: Kishore Babu Kavuru Commit trigger to Pipeline job using github-webhook is not working. 503- response in the hook. Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

[anuragsrivastava234@gmail.com (JIRA)]

Anurag Srivastava updated an issue

Jenkins / JENKINS-59876 Github orgnization commit trigger to build pipeline is not working through scm polling

Change By: Anurag Srivastava Attachment: buildtrigger.PNG Attachment: GitHub_error.png Attachment: Webhook_error.png

Add Comment

[anuragsrivastava234@gmail.com (JIRA)]

Anurag Srivastava commented on JENKINS-59876

Re: Github orgnization commit trigger to build pipeline is not working through scm polling Trying to integrate Jenkins pipeline job with GitHub enterprise through 'github-webhook'. Steps: 1- Create webhook in our GitHub Repo. ex: http://xxxxxxx.india.xorg.com:8080/github-webhook/ (push) 2- Create Jenkins pipeline Project.    i- In General section select GitHub project and provide Project SSH URL. ex: g...@github.yorg.com:xyz/abc-test/   ii- In Build Trigger section select "GitHub hook trigger for GITScm polling". Even tried with Poll SCM for 1minute, its not able to check the changed log of github repo.   iii- In Pipeline section, tried with both "Pipeline script" and "Pipeline script from SCM".   Response, error:503 Notification codes:  (1, DNS_FAIL, sys_name.india.xorg.com)

Add Comment

[babu.kishore26@gmail.com (JIRA)]

Kishore Babu Kavuru commented on JENKINS-59876

Re: Github orgnization commit trigger to build pipeline is not working through scm polling

Thanks anurag your comments would be helpful. Hi Mark Waite, please let us know if require any further information. Thanks in advance.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-59876

Re: Github orgnization commit trigger to build pipeline is not working through scm polling

HTTP 503 is used to indicate that a service is down. I assume that 503 is what was reported by your GitHub server. If so, then check that your GitHub enterprise server can resolve the DNS name of the computer you listed as sys_name.india.xorg.com. If the 503 was reported by the Jenkins server, then check that your Jenkins server can resolve the DNS name of the computer you listed as sys_name.india.xorg.com. These types of questions are best handled as questions in the user mailing list or in one of the chat systems, not as bug reports. It is not a Jenkins bug that the DNS server in your organization cannot resolve a particular hostname.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-59876

Github orgnization commit trigger to build pipeline is not working through scm polling

Change By: Mark Waite Assignee: Mark Waite

Add Comment

[babu.kishore26@gmail.com (JIRA)]

Kishore Babu Kavuru updated an issue

Jenkins / JENKINS-59876

Github orgnization commit trigger to build pipeline is not working through scm polling

Change By: Kishore Babu Kavuru Issue Type: Bug Story

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite closed an issue as Not A Defect

Jenkins / JENKINS-59876 Github orgnization commit trigger to build pipeline is not working through scm polling

Change By: Mark Waite Status: Open Closed Resolution: Not A Defect

Add Comment

[babu.kishore26@gmail.com (JIRA)]

Kishore Babu Kavuru commented on JENKINS-59876

Re: Github orgnization commit trigger to build pipeline is not working through scm polling Yes, I think we are on the same page 503 is reported by Github server webhook only. let me confirm on my understanding if Jenkins is on 'xorg' intranet only and not resolved on Github 'yorg' DNS server this issue persists. But I'm facing a similar issue when both the Jenkins and Github are on the same 'yorg' intranet (DNS resolved), it's throwing a 'timeout' response on Github-webhook.

Add Comment

[babu.kishore26@gmail.com (JIRA)]

Kishore Babu Kavuru reopened an issue

github-webhook throghs 307 response code "(1, SERVER_NAME_EXPANSION, , xyz_system_name)"

Jenkins / JENKINS-59876

Github orgnization commit trigger to build pipeline is not working through scm polling

Change By: Kishore Babu Kavuru

Resolution: Not A Defect Status: Closed Reopened Assignee: Mark Waite

Add Comment

[babu.kishore26@gmail.com (JIRA)]

Kishore Babu Kavuru commented on JENKINS-59876

Re: Github orgnization commit trigger to build pipeline is not working through scm polling Seriously we are seeking for help, we don't any other platform for QnA. thanks for your patience.

Add Comment

[babu.kishore26@gmail.com (JIRA)]

Kishore Babu Kavuru edited a comment on JENKINS-59876

Re: Github orgnization commit trigger to build pipeline is not working through scm polling

Seriously we are seeking for help, we don't find any other platform for QnA. thanks for your patience.

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite commented on JENKINS-59876

Re: Github orgnization commit trigger to build pipeline is not working through scm polling

Please refer to https://jenkins.io/mailing-lists/ for the mailing lists. Please refer to https://jenkins.io/chat/ for the chat channels. You're asking for help in a forum that is monitored by very few people (mostly me, maybe 3-5 others). When you ask for help in the mailing lists, you're asking for help from a forum that is read by many, many more people. When you ask for help in the chat channels, you're asking for help in a forum that is read by many more people. You'll get better results from a request for help in forums that are designed to provide help because there are more people available in those places to help you there are broader experiences in those places

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite closed an issue as Not A Defect

Jenkins / JENKINS-59876

Github orgnization commit trigger to build pipeline is not working through scm polling

Change By: Mark Waite Status: Reopened Closed Resolution: Not A Defect

Add Comment

[mark.earl.waite@gmail.com (JIRA)]

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-59876 Github orgnization commit trigger to build pipeline is not working through scm polling

Change By: Mark Waite Assignee: Mark Waite

Add Comment