hook declined to update branch
From admin page: GitLab 6.6.4 GitLab Shell 1.8.0 GitLab API v3 Ruby 2.0.0p353 Rails 4.0.3
When pushing to a branch that is not master we see:
git -c diff.mnemonicprefix=false -c core.quotepath=false push -v --tags origin develop:develop feature/v_1_5_x:feature/v_1_5_x master:master
Pushing to http://gitlab.ara.wan/software/vertekcals-v1.git
POST git-receive-pack (1857 bytes)
remote: /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/spec_set.rb:92:in `block in materialize': Could not find rake-10.1.1 in any of the sources (Bundler::GemNotFound)[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/spec_set.rb:85:in `map!'[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/spec_set.rb:85:in `materialize'[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/definition.rb:133:in `specs'[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/definition.rb:178:in `specs_for'[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/definition.rb:167:in `requested_specs'[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/environment.rb:18:in `requested_specs'[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/runtime.rb:13:in `setup'[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler.rb:119:in `setup'[K
remote: from /home/git/.rbenv/versions/2.0.0-p353/lib/ruby/gems/2.0.0/gems/bundler-1.5.1/lib/bundler/setup.rb:17:in `<top (required)>'[K
remote: from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'[K
remote: from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require'[K
remote: error: hook declined to update refs/heads/feature/v_1_5_x[K
To http://gitlab.ara.wan/software/vertekcals-v1.git
= [up to date] develop -> develop
= [up to date] master -> master
! [remote rejected] feature/v_1_5_x -> feature/v_1_5_x (hook declined)
updating local tracking ref 'refs/remotes/origin/develop'
updating local tracking ref 'refs/remotes/origin/master'
error: failed to push some refs to 'http://gitlab.ara.wan/software/vertekcals-v1.git'The server serves other things besides gitlab and so has ruby 1.9.3p194 as the system ruby. We use rbenv to make sure that gitlab runs at 2.0-p353 which works great until we push to remote branches like above.
This does not occur with versions prior to 6.6.
Activity
I'm having the same issue, rake 10.1.1 is installed in the system and in the bundle:
root@myhost:~$ rake --version rake, version 10.1.1 git@myhost:~/gitlab$ bundle exec rake --version rake, version 10.1.1A workaround has been to change the shebang from the update hook in the repos (/home/git/repositories/reponame.git/hooks/update) from this:
#!/usr/bin/env rubyto the ruby 2.0 binaries:
#!/usr/local/bin/rubyI had the same issue with my ubuntu 14.04 lts + rvm gitlab installation. The problem here was the ruby installed from apt. I've removed it via
sudo aptitude remove rubyand ranrvmsudo -u git -H bundle install --deployment --without development test postgres awsin/home/git/gitlaband restarted gitlab (sudo /etc/init.d/gitlab restart). After that it worked.FWIW, I got a similar error:
remote: /opt/bitnami/ruby/lib/ruby/1.9.1/net/http.rb:763:in `initialize': No route to host - connect(2) (Errno::EHOSTUNREACH) remote: from /opt/bitnami/ruby/lib/ruby/1.9.1/net/http.rb:763:in `open' remote: from /opt/bitnami/ruby/lib/ruby/1.9.1/net/http.rb:763:in `block in connect' remote: from /opt/bitnami/ruby/lib/ruby/1.9.1/timeout.rb:55:in `timeout' remote: from /opt/bitnami/ruby/lib/ruby/1.9.1/timeout.rb:100:in `timeout' remote: from /opt/bitnami/ruby/lib/ruby/1.9.1/net/http.rb:763:in `connect' remote: from /opt/bitnami/ruby/lib/ruby/1.9.1/net/http.rb:756:in `do_start' remote: from /opt/bitnami/ruby/lib/ruby/1.9.1/net/http.rb:745:in `start' remote: from /opt/bitnami/apps/gitlab/gitlab-shell/lib/gitlab_net.rb:76:in `get' remote: from /opt/bitnami/apps/gitlab/gitlab-shell/lib/gitlab_net.rb:31:in `allowed?' remote: from /opt/bitnami/apps/gitlab/gitlab-shell/lib/gitlab_update.rb:39:in `exec' remote: from hooks/update:13:in `<main>'This is using the bitnami virtual machine. However, I think it was because the IP address of the server had changed due to DHCP on the bridge, but not all the services were properly updated. No idea if this is a bug with bitnami or gitlab, but in any case a reboot solved the problem. Restarting the services might also have resolved the problem, but I didn't think to try that.
