Jenkins Pull Request Builder issue when serving two github enterprise instances?

Multi tool use
Multi tool use


Jenkins Pull Request Builder issue when serving two github enterprise instances?



We hosted 2 different github instances, say, one is configured as http://git.domain1.com/ while the other http://git.domain2.com/.



Then on a same Jenkins server, I set up 2 jobs for 2 different repos, respectively. One repo is from domain1 and the other from domain2.



Both jobs are configured to Use github hooks for build triggering.



Now the problem is, pull request from either repo will simply trigger both Jenkins jobs to run. So there is always one build making no sense at all and is doomed to fail.



I guess it was partly because both repoes are configured with exactly the same hook url: http://our-jenkins.com:8080/ghprbhook/ (but we do have only one Jenkins server).



Another part of the reason may be "Use github hooks for build triggering", which makes the jobs simply wait for hook request passively, without honoring what I configured in "Project URL" and "Repository URL".



But how can I get out of this situation?









By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

xs9M9RBQfzUNmAyaT Ky8yAsV77VbU,TaCSsBpH,JYmwYaa 3C quKQaoR
GaT jfwLBhNYEkAY,bxgEIDRsVz rzd7eggC4VDz IQ,zGyV74bfkz

Popular posts from this blog

PHP contact form sending but not receiving emails

Do graphics cards have individual ID by which single devices can be distinguished?

Create weekly swift ios local notifications