Conversation RepositoryService::FetchRemote
Feature Flag: gitaly_fetch_remote
Depends on #386 (closed).
Stages:
-
RPC Design: #455 (closed) https://gitlab.com/gitlab-org/gitaly-proto/merge_requests/62 -
Server Implementation: #439 (closed) !276 (merged) !300 (merged) -
Client Implementation: #440 (closed) gitlab-org/gitlab-ce!13625 -
Acceptance Testing: https://gitlab.com/gitlab-org/gitaly/issues/578
RPC Endpoints:
Endpoint::Name
Known Client Routes:
- Known client endpoints
Gitlab::Shell gitlab-projects methods
In gitlab-ce's Gitlab::Shell we have a bunch of methods that shell out to gitlab-shell/bin/gitlab-projects. This should go through RPC calls. Gitlab-shell will be installed on the Gitaly server and Gitaly will 'know' where the gitlab-shell directory is #386 (closed).
Related to https://gitlab.com/gitlab-org/gitaly/issues/391
service RepositoryService {
rpc FetchRemote(FetchRemoteRequest) returns (FetchRemoteResponse) {}
}
message FetchRemoteRequest {
Repository repository = 1;
string remote = 2;
bool force = 3;
bool no_tags = 4;
}
message FetchRemoteResponse {
bool ok = 1;
}