Organization of work of programmers with SVN and Jenkins for deployment

Question

Programming

Given: SVN server, Jenkins, which collects projects from sources (pulls via SVN) and deploys them to servers. To make it as fast as possible, the machine with Jenkins and SVN is located next to the servers to which it deploys (in the data center).

Problem: when the Internet disappears ( Ukrtelecom, be it wrong ), the work of programmers is stopped, because The SVN server is far away, not local.

We are thinking of moving the SVN server to the programmers' office, but then the question arises of how to deal with Jenkins, also transfer it (because there is no access to the local SVN from the data center where Jenkins is currently installed)? If we transfer everything to the office, then the deployment process will be delayed ( due to the low return speed of Ukrtelecom), because it will take time to copy the collected projects to the servers that are in the data center.

Another option is to connect a second provider and configure the gateway so that if one provider has an Internet connection, the second one automatically rises.

Share your experience, how it works for you.

Answer 1

I don't know how your project is set up, but if your Jenkins deploys from the same branch (trunk), then it should have a working copy that it updates with each deploy. Accordingly, it should only download changes, and not the entire branch, which means there should not be so much traffic. I think you can easily check this by raising Jenkins in your office and watching how it will build the project from a remote repository.
In general, in your situation, git is crying for you :)

Answer 2

How do you copy from Jenkins to the servers? What is the file size?

Answer 3

If there is no access to the office from the data center, then you can try to set up a mirror for SVN blog.notreally.org/2006/11/30/setting-up-a-subversion-mirror-repository-using-svnsync/
That is, the office should be configured hooks that synchronize the office SVN with the SVN in the data center.

Answer 4

why the work is stopped is not clear, write and write code for yourself in the local version, there is an Internet commit.

Answer 5

Try catlight to monitor Jenkins.