Defect #8049
closed
Git: fetch_changesets not updating project's repository
Added by Yang Zhang over 13 years ago. Updated over 13 years ago.
0%
Description
rake -f /.../redmine/Rakefile redmine:fetch_changesets RAILS_ENV=production no longer seems to be working on my project's git repo. The last known commit was from 22d ago. Running the rake job produces no output (besides (in /root). How do I get to the bottom of this?
Related issues
Updated by Toshi MARUYAMA over 13 years ago
- Status changed from New to Closed
- Resolution set to Duplicate
Duplicate of #7146.
Updated by Yang Zhang over 13 years ago
- Status changed from Closed to Reopened
Toshi, we don't have any non-master branches - are you sure this is a duplicate?
Updated by Toshi MARUYAMA over 13 years ago
- Status changed from Reopened to Closed
Yes. You need to use bare repository.
Updated by Yang Zhang over 13 years ago
Um, it is a bare repo:
$ ls /var/git/sales.git/ branches/ description hooks/ objects/ packed-refs config HEAD info/ ORIG_HEAD refs/
Updated by Toshi MARUYAMA over 13 years ago
- Subject changed from fetch_changesets not updating project's repository to Git: fetch_changesets not updating project's repository
Updated by Toshi MARUYAMA over 13 years ago
- Status changed from Reopened to Closed
Redmine runs "git branch" at source:tags/1.1.2/lib/redmine/scm/adapters/git_adapter.rb#L38 .
Updated by Yang Zhang over 13 years ago
- Status changed from Closed to Reopened
Toshi, we are using 1.0.5 (we cannot upgrade), and the code is the same: source:tags/1.0.5/lib/redmine/scm/adapters/git_adapter.rb#L38.
As I mentioned, we have no non-master branches:
$ git branch * master
Also, our problem hasn't been resolved - why are you repeatedly closing this ticket?
Updated by Toshi MARUYAMA over 13 years ago
> $ git branch > * master >
It means you don't have branches except master.
You need to push other branches to your bare repsitory.
$ git push origin branch:branch
Updated by Toshi MARUYAMA over 13 years ago
- Status changed from Reopened to Closed
Updated by Toshi MARUYAMA over 13 years ago
- Resolution changed from Duplicate to Invalid
Updated by Yang Zhang over 13 years ago
- Status changed from Closed to Reopened
Toshi, that doesn't work - see below, Redmine's still not updating properly. Why do you keep marking this closed? And why is this marked Invalid?
$ git branch testing $ git branch * master testing
Updated by Toshi MARUYAMA over 13 years ago
- Status changed from Reopened to Closed
This is redmine issue tracker.
You should use redmine forum.
Updated by Toshi MARUYAMA over 13 years ago
Try "git log --all" or "gitk --all" on your bare repository.
Updated by Toshi MARUYAMA over 13 years ago
- Resolution changed from Invalid to Duplicate
Updated by Toshi MARUYAMA over 13 years ago
Your description "The last known commit was from 22d ago" means known 7 days problem.
If you still have problem, you should not post to this issue, you should post to #7146.
Updated by Yang Zhang over 13 years ago
git log --all shows our most recent commits just fine (from yesterday).
Yes, I mentioned "22d ago" and the other ticket is titled "before 7 days," but that doesn't imply it's the same problem.
I've moved this to the forum: http://www.redmine.org/boards/2/topics/23033
Updated by Toshi MARUYAMA over 13 years ago
Yang Zhang wrote:
Yes, I mentioned "22d ago" and the other ticket is titled "before 7 days," but that doesn't imply it's the same problem.
I have changed #7146 title.