Project

General

Profile

Actions

Defect #7146

closed

Git adapter lost commits before 7 days from database latest changeset

Defect #7146: Git adapter lost commits before 7 days from database latest changeset

Added by Hugo Raben almost 16 years ago. Updated over 15 years ago.

Status:
Closed
Priority:
Low
Assignee:
Toshi MARUYAMA
Category:
SCM
Target version:
Resolution:
Fixed
Affected version:

Description

Hi,

We work with several branches on a git repo, but Redmine only seems to track changes from master branch. The problem is that our commit messages like:
"Fixes #241"... do not work if they are created on a "develop" branch for example. Redmine does not "see" these commit messages, therefore it can't mark the bug as fixed.

This seems to be a bug implementation of issue #1406

Database version : Postgresql 8.3
git version: 1.5.6.5
Redmine version: 1.0.4


Related issues 11 (3 open — 8 closed)

Related to Redmine - Defect #6013: git tab,browsing, very slow -- even after first timeClosedActions
Related to Redmine - Defect #4549: Repository: git / view all revision fails with branchesClosedActions
Related to Redmine - Feature #6092: Truncate Git revision labels in Activity page/feed and allow configurable lengthClosedToshi MARUYAMAActions
Related to Redmine - Defect #5357: Git: SCM revisions ordered by date/time (should be reverse commit order)NewToshi MARUYAMAActions
Related to Redmine - Feature #2799: Support for Bazaar's shared reposetories (created with init-repo)NewActions
Related to Redmine - Feature #6566: Convert the git adapter to ruggedNewActions
Related to Redmine - Defect #8857: Git: Too long in fetching repositories after upgrade from 1.1 or new branch at first timeClosedToshi MARUYAMAActions
Related to Redmine - Defect #9472: The git scm module causes an excess amount of DB traffic.ClosedActions
Has duplicate Redmine - Defect #3940: Git: The entry or revision was not found in the rebased repositoryClosedActions
Has duplicate Redmine - Defect #8049: Git: fetch_changesets not updating project's repositoryClosedActions
Has duplicate Redmine - Defect #8256: 404 on repository revision access using gitClosedActions

Updated by Toshi MARUYAMA almost 16 years ago Actions #1

The reason is Redmine parse only 1 week before the last known commit.

See source:tags/1.0.4/app/models/repository/git.rb#L48

Updated by Toshi MARUYAMA almost 16 years ago Actions #2

This issue is related with #6013.

Updated by Toshi MARUYAMA over 15 years ago Actions #3

  • Affected version (unused) changed from 1.0.4 to 0.9.3
  • Affected version changed from 1.0.4 to 0.9.3

Updated by Toshi MARUYAMA over 15 years ago Actions #4

  • Subject changed from Make Redmine follow changes from Git non-master branches to Git adapter lost commits before 7 days
  • Priority changed from Normal to Low

Updated by Toshi MARUYAMA over 15 years ago Actions #5

  • Subject changed from Git adapter lost commits before 7 days to Git adapter lost commits before 7 days from database latest changeset

Updated by Toshi MARUYAMA over 15 years ago Actions #6

Redmine calls "git log --all --since='YYYY-MM-DD'" to fetch new changesets.
at source:1.1.2/lib/redmine/scm/adapters/git_adapter.rb#L114 .

If latest changeset in your database is "2011-03-30", Redmine calls "git log --all --since='2011-03-23'".

Updated by Ling Li over 15 years ago Actions #7

I am curious: Do the commits you mentioned in #8256 for ChiliProject also go to Redmine? I am confused by how these two projects progress --- would they share most of the new changes?

Updated by Toshi MARUYAMA over 15 years ago Actions #8

  • Assignee set to Toshi MARUYAMA

Updated by Toshi MARUYAMA over 15 years ago Actions #9

  • Status changed from New to Closed
  • Target version set to 1.2.0
  • Resolution set to Fixed

Fixed in r5788.

Actions

Also available in: PDF Atom