| commit | a15181b1b88ed69c04ca7ea0d23a3777b7f53a4e | [log] [tgz] |
|---|---|---|
| author | Fabio Ponciroli <ponch78@gmail.com> | Wed Aug 13 11:06:13 2025 -0600 |
| committer | Fabio Ponciroli <ponch78@gmail.com> | Tue Aug 19 11:17:33 2025 +0200 |
| tree | b67a52c570d5a23c4cffc09be03033d7c9e895a0 | |
| parent | dfef6cada6e73e6b5b93959b8cc154e490e5cf75 [diff] | |
| parent | 2adae4632e3bb6d64831c74534f08068ec4635e5 [diff] |
Merge branch 'stable-3.12' * stable-3.12: Log cancelled fetch collisions without reschedule Add per-project shared lock to avoid fetch collisions Revert "Prevent concurrent fetches on the same repository" Revert "Extract QueueInfo into its own class" Extract QueueInfo into its own class Throw LockFailureException from filterAndLock interface Expose new constructor for LockFailureException Prevent concurrent fetches on the same repository Change-Id: I2b8240bb840056d1f836d8a98d651f7115e1d96b
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