From 9785f535c6d7e6a6f0bc3192a7c1d38dea4fd88f Mon Sep 17 00:00:00 2001 From: Jacob Vosmaer Date: Wed, 5 Feb 2014 18:20:51 +0100 Subject: [PATCH] Explain the REVISION hack --- config/software/gitlab-core.rb | 5 +++++ 1 file changed, 5 insertions(+), 0 deletions(-) diff --git a/config/software/gitlab-core.rb b/config/software/gitlab-core.rb index efa57a9..46936da 100644 --- a/config/software/gitlab-core.rb +++ b/config/software/gitlab-core.rb @@ -30,6 +30,11 @@ dependency "postgresql" source :git => "https://gitlab.com/gitlab-org/gitlab-ce.git" build do + # GitLab assumes it can extract the Git revision of the currently version + # from the Git repo the code lives in at boot. Because of our rsync later on, + # this assumption does not hold. The sed command below patches the GitLab + # source code to include the Git revision of the code included in the omnibus + # build. command "sed -i 's/.*REVISION.*/REVISION = \"#{version_guid.split(':').last[0,10]}\"/' config/initializers/2_app.rb" bundle "install --without mysql development test --path=#{install_dir}/embedded/service/gem" command "mkdir -p #{install_dir}/embedded/service/gitlab-core" -- libgit2 0.21.2