Redmine

It seems that the problem is in the update hook:

/usr/share/gitolite/hooks/common/update

There is following code:

BEGIN {
    # people with shell access should be allowed to bypass the update hook,
    # simply by setting an env var that the ssh "front door" will never set
    exit 0 if exists $ENV{GL_BYPASS_UPDATE_HOOK};

    die "ENV GL_RC not set\n" unless $ENV{GL_RC};
    die "ENV GL_BINDIR not set\n" unless $ENV{GL_BINDIR};
}

The error show that the push fails at:

die "ENV GL_RC not set\n" unless $ENV{GL_RC};

but as I understand (from what I read so far) the update script should already exited the line before at:

exit 0 if exists $ENV{GL_BYPASS_UPDATE_HOOK};

because it should bypass the update hook. The Question is why is GL_BYPASS_UPDATE_HOOK not existing nad where could we set it so the update hook will be bypassed? Is it in Redmine or in the gitolite plugin where this variable should be set and where? Do someone have an idea?

Update:
Hi again,

i searched the gitolite plugin an found that in the version 1.1.x there was in the file:

/opt/redmine/redmine-3.2.0/plugins/redmine_git_hosting/lib/grack/server.rb

this code:

def smart_http_args
['env', 'GL_BYPASS_UPDATE_HOOK=true']
end

but in the Version 1.2.0 we are using this is missing, so i added it manually in this form to workaraound the problem for now, bevor:

      def smart_http_args
        [
          'env',
          "GL_LIBDIR=#{RedmineGitHosting::Config.gitolite_lib_dir_path}",
          "GL_REPO=#{repository_object.gitolite_repository_name}",
          "GL_USER=#{@env['REMOTE_USER']}",
       ]
      end

after:

      def smart_http_args
        [
          'env',
          "GL_LIBDIR=#{RedmineGitHosting::Config.gitolite_lib_dir_path}",
          "GL_REPO=#{repository_object.gitolite_repository_name}",
          "GL_USER=#{@env['REMOTE_USER']}",
          "GL_BYPASS_UPDATE_HOOK=1" 
        ]
      end

After this change push is working again. The question now is, was this removed on any reason or is this maybe a bug in the 1.2.0 Version of this plugin?

By now i did not see any side effects of the change, but I also have to confese that this is the first time i working with git and I do not exactly know why the update has to be bypased and what the update is exactly doing and if it could have an impact on my data?

Kind regards,
Michael

Michael Stang wrote:

It seems that the problem is in the update hook:

I found a better solution ;-)