I'd like to use GitLab CI in a private network (data enter environment /VPS), with GitHub hosting the code repos and commits to those repos triggering a build on the GitLab CI which will then deploy artifacts to servers in the same private network the CI server is hosted in.
I can do this easily with GitLab deployed to AWS with a public address which allows GitHub to do callbacks to Gitlab, however, the environment I want has the following constraints: 1. No public address is exposed on the private network - so the GitLab server cannot be directly reached by connections initiated from GitHub (due to security policies). 2. The source code from the repos cannot be mirrored in GitLab for longer than the build-deploy phase requires it (due to security policies). So we cannot use GitLab as a repo mirror of some kind on the private network. My question is: What solutions are there to address this scenario? So far, the only solutions I can think of involve: a) GitLab polling gitHub (frequently) for recent changes to the git repo and triggering the build if new changes are registered. However, I think this would be difficult to do without retaining a copy of the source repo in GitLab itself ... b) Creating a secure, public address for the gitlab server, and locking access down to GitHub's CIDR ranges (however I've never seen a defined whitel-listable set of addresses or GitHub, so this solution is not likely) Any advice on this would be greatly appreciated! TGW -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/cc95d6ae-11c7-455e-9025-27198ed5cfbc%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
