We have two teams who work on the same project. Each team is on a different network. Unfortunately, none of these networks is connected to the internet and due to the rules of the company, this project is not allowed to transfer any data over the Internet. We can only transfer files between the two periodically, which is the only connection.
Ideally, each team should be able to clone, commit and push a bare. Whenever we want to synchronize the repo on our network, we can transfer any kind of (binary) difference / patches between those sites which will be used to sync the repo.
The method that is currently being used: We have a single at-jet repo located on Network A. A. Team A is happy every time the developers want to sync their changes with Network B, they make series with random repo from previous sync, give them to Team A, team A network introduces patch on A repo. Sometimes we change the bare with network copy of a repo from Network A to A, so that the developer changes on Network B can be dragged.
What is wrong with this method? 1. We have "up to date" repo on site A. Team B needs to apply on site A to make patches and sync their work. 2. We periodically transfer the whole repo between the sites, not the only difference (whenever we want to draw on site B) 3. The developers of Site B are not putting pressure on the bare repo (only make patch for Team A).
Thank you!
OK, for a clear solution, a GIT repository will be hosted online, which will push / This is the standard way you can bridge, you can also use Geethhub.
No comments:
Post a Comment