Encapsulate all meta ref revisions in the same apply-object When a batch-apply-object fails, usually because of a missing parent exception, the whole history for the ref in question was sent as a separate HTTP call before the batch was retried. This caused the batch to essentially be split into two updates, one for the meta and one for everything else, breaking the very basic principle for which batch-apply-object was introduced. Introduce a new BatchApplyObjectsData, which allows applying multiple objects for a set of refs within a single batch. Bug: Issue 529852969 Change-Id: I67c3ba118a97076eb61aa5d4e61b0cf3a3f3d7ff
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