| commit | 5557818c449cd88a1d2951ca14496fbf6675b3f2 | [log] [tgz] |
|---|---|---|
| author | Luca Milanesio <luca.milanesio@gmail.com> | Sat Mar 22 10:49:06 2025 +0000 |
| committer | Luca Milanesio <luca.milanesio@gmail.com> | Sat Mar 22 10:49:06 2025 +0000 |
| tree | 7bfcda86ebb79515c2f63729545088b27aa440a7 | |
| parent | f426afbc98efb346538d26cf08cdaafd75827060 [diff] | |
| parent | 1f3fb748c8732fcc57185f3a7faca7fe3aa327b2 [diff] |
Merge branch 'stable-3.11' * stable-3.11: Do not lock refs when not executing a fetch Allow locking refs whilst filtering for fetch requests Remove unused Transport in FetchOneTest Avoid mocking ReplicationFetchFilter Remove redundant public modifier in ReplicationFetchFilter Record replication metrics for retrying tasks Change-Id: I63317ad5f0f98e988844bf40f81522fec014641a
This plugin can automatically mirror repositories from other systems.
Typically replication should be done over SSH, with a passwordless public/private key pair. On a trusted network it is also possible to use replication over the insecure (but much faster due to no authentication overhead or encryption) git:// protocol, by enabling the upload-pack service on the receiving system, but this configuration is not recommended. It is also possible to specify a local path as replication source. This makes sense if a network share is mounted to which the repositories should be replicated from.
To be allowed to trigger pull replication a user must be a member of a group that is granted the ‘Pull Replication’ capability (provided by this plugin) or the ‘Administrate Server’ capability.
Changes will be automatically indexed upon replication.
For more information please refer to the docs