You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The repo page isn't updated in Redmine after an initial git push.
Create new project/repo -- repo is empty
I see the empty repo page
I do the initial push from my local
I still see the empty repo page
I manually run the rake task fetch_changesets
Repo page is now updated
I make a new commit and push
Repo page is updated immediately
My current workaround is I added a cron job to run the fetch_changesets rake task every hour, such that newly-created projects/repos will show up, after a while.
Ruby: 2.0.0-p598
Redmine: 2.6.0.stable
Git: 1.9.5
redmine_git_hosting: v1.x branch
Gitolite: 3.6.2
The text was updated successfully, but these errors were encountered:
I mentioned in #336 (comment) that I had Ruby 1.8.7 in my system, and that I didn't see any additional output for git push -u origin master, so I guessed that the hooks weren't executed at all.
I upgraded my system Ruby, and the git hooks now work. I installed the latest Ruby, 2.2, so I'm not sure what the correct minimum version really is (1.9?, 2.0?).
Our post-receive hook is triggered after each commit and is used to fetch changesets in Redmine. As it is written in Ruby, you need to install Ruby on your server. Note that this does not conflict with RVM.
So I simply installed from yum on CentOS 6, and that's what gave me Ruby 1.8.
I upgraded my system Ruby, and the git hooks now work. I installed the latest Ruby, 2.2, so I'm not sure what the correct minimum version really is (1.9?, 2.0?).
It should work with Ruby 1.9.
BTW, the installation doc does not specify a minimum system Ruby version
"Forked" from #336 (comment) :
The repo page isn't updated in Redmine after an initial
git push
.fetch_changesets
My current workaround is I added a cron job to run the
fetch_changesets
rake task every hour, such that newly-created projects/repos will show up, after a while.The text was updated successfully, but these errors were encountered: