From bbccd310573bb70e6b413c2bde915fcb8810716e Mon Sep 17 00:00:00 2001
From: Zeger-Jan van de Weg <git@zjvandeweg.nl>
Date: Thu, 19 Apr 2018 10:40:28 +0200
Subject: [PATCH] Check Gitaly when running `rake dev:setup`

Before this change, trying to setup dev environment could be tried
without having at least one Gitaly running. Cloning the repositories
would fail, but not stop the setup.

Given this would lead to an inconsistent state, a check was added if we
could connect to the server.

Output when it fails:

```
$ rake dev:setup
Failed to connect to Gitaly...
Error: 14:Connect Failed
```
---
 lib/tasks/gitlab/setup.rake | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/lib/tasks/gitlab/setup.rake b/lib/tasks/gitlab/setup.rake
index 1d903c81358..f71e69987cb 100644
--- a/lib/tasks/gitlab/setup.rake
+++ b/lib/tasks/gitlab/setup.rake
@@ -1,9 +1,20 @@
 namespace :gitlab do
   desc "GitLab | Setup production application"
   task setup: :gitlab_environment do
+    check_gitaly_connection
     setup_db
   end
 
+  def check_gitaly_connection
+    Gitlab.config.repositories.storages.each do |name, _details|
+      Gitlab::GitalyClient::ServerService.new(name).info
+    end
+  rescue GRPC::Unavailable => ex
+    puts "Failed to connect to Gitaly...".color(:red)
+    puts "Error: #{ex}"
+    exit 1
+  end
+
   def setup_db
     warn_user_is_not_gitlab