Hi All,
I am a Systems Administrator who was recently asked to perform a Jenkins/GitHub integration.

The requirements are...

1) When a GitHub pull request is made, start a Jenkins build.
2) Tell GitHub through the APIs that a Jenkins build is running.
3) When the Jenkins build finishes, inform GitHub that the Jenkins build succeeded/failed. 4) Update the GitHub pull request with a comment containing the URL of the webapp built for the branch after having deployed it.

I am being told by my internal Developers that Requirement # 1 involves exposing my Jenkins server to the 1000+ GitHub IPs [as documented below]:
https://help.github.com/articles/what-ip-addresses-does-github-use-that-i-should-whitelist

The most secure of the two options [HTTPS with HTTP Basic Auth] presented at the above link has me confused though... Where do we configure the username and password for the HTTPS with HTTP Basic Auth in GitHub? I know how to configure it on my end, but how do I tell GitHub about it - so that the GitHub POST to my Jenkins server will actually succeed?

Also, is there any way to meet the above requirements without exposing my Jenkins server to GitHub?

Please let me know how most folks meet the aforementioned requirements - as I am told that this is already a solved problem for many shops.

BTW, we are pretty certain that we will need the following plugin:
https://wiki.jenkins-ci.org/display/JENKINS/Github+pull+request+builder+plugin

However, I am not quite sure how to leverage it at the moment.

Please advise.

Thanks,
Mike

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to