| commit | c9491076e2b27cf753886ef3e982cda378336305 | [log] [tgz] |
|---|---|---|
| author | Fabio Ponciroli <ponch78@gmail.com> | Wed May 21 18:13:05 2025 +0200 |
| committer | Fabio Ponciroli <ponch78@gmail.com> | Wed May 21 18:13:05 2025 +0200 |
| tree | 119f462fd2fb4783ab3dbda1471974852ae2e797 | |
| parent | 5557818c449cd88a1d2951ca14496fbf6675b3f2 [diff] | |
| parent | 7532ea37e8addde175ed8a357c5c5391060f287f [diff] |
Merge branch 'stable-3.11' into stable-3.12 * stable-3.11: Do not notify failures on collisions Fixed erroneous increment of the rescheduled metric Ensure failures are only incremented in RunnableWithMetrics Move ProjectDeletionAction/CacheDeleteHandler PullReplicationModule Change-Id: Idf22185207dc94bd184be6e4130e526ef16a2ca5
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