commit | 51962af0696a9c8b7875e7c0fe0e0b1f3168bee4 | [log] [tgz] |
---|---|---|
author | David Pursehouse <dpursehouse@collab.net> | Fri Oct 12 07:54:16 2018 +0900 |
committer | David Pursehouse <dpursehouse@collab.net> | Thu Oct 11 23:11:23 2018 +0000 |
tree | a950636f1b221faf1b2e91158fecc0f74e067b6d | |
parent | 9a2d8ecda1577f0305423aff5fd602c6f0baa745 [diff] |
bazlets: Replace native.git_repository with skylark rule The native.git_repository rule does not work properly when invoked in a `git submodule foreach` command. Bazel will deprecate the native rules anyway, so replace with skylark's git_repository. See [1] for context. [1] https://github.com/bazelbuild/bazel/issues/6358#issuecomment-429103745 Change-Id: I1862ed62df1018df30fabcaeb818020cbf3f97cf
The importer plugin allows to import projects from one Gerrit server into another Gerrit server.
Projects can be imported while both source and target Gerrit server are online. There is no downtime required.
The git repository and all changes of the project, including approvals and review comments, are imported. Historic timestamps are preserved.
Project imports can be resumed. This means a project team can continue to work in the source system while the import to the target system is done. By resuming the import the project in the target system can be updated with the missing delta.
The importer plugin can also be used to copy a project within one Gerrit server, and in combination with the delete-project plugin it can be used to rename a project.