Gitaly and Workhorse will always restart upon timestamp updates
Upon testing @balasankarc's changes in !2590 (merged), I noticed:
- update content in file /var/opt/gitlab/gitaly/VERSION from 075715 to a1ba01
--- /var/opt/gitlab/gitaly/VERSION 2018-06-15 12:23:05.977611595 +0000
+++ /var/opt/gitlab/gitaly/.chef-VERSION20180618-24210-fk4qmu 2018-06-18 13:32:46.702679139 +0000
@@ -1,2 +1,2 @@
-Gitaly, version 0.107.0-2-gdf6b83ec, built 20180615.025842
+Gitaly, version 0.107.0-2-gdf6b83e, built 20180618.043603
Also:
* file[/var/opt/gitlab/gitlab-workhorse/VERSION] action create
- update content in file /var/opt/gitlab/gitlab-workhorse/VERSION from 4f7c3a to 0c038c
--- /var/opt/gitlab/gitlab-workhorse/VERSION 2018-06-15 12:23:05.209536484 +0000
+++ /var/opt/gitlab/gitlab-workhorse/.chef-VERSION20180618-24210-hsvmsw 2018-06-18 13:32:45.978608331 +0000
@@ -1,2 +1,2 @@
-gitlab-workhorse v4.3.1-2-g3ec9de6-20180615.024805
+gitlab-workhorse v4.3.1-2-g3ec9de6-20180618.042423
In both cases, both Gitaly and Workhorse didn't change, but because of the build timestamps we'll always restart the processes.
I assume this is intentional, but wanted to raise this as a point because I assume the same thing applies to GitLab Pages?