Project

General

Profile

Actions

Defect #8030

open

Bazaar integration doesn't notice new commits to repository

Added by Radosław Grzanka almost 13 years ago. Updated almost 13 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
2011-03-31
Due date:
% Done:

0%

Estimated time:
Resolution:
Affected version:

Description

Redmine fetches new revisions from repository to its own database when revision identifier in db is lower then in current branch of repository.

For finding out revision identifier it uses "bzr revno <tree>". However, this number in bazaar is not guaranteed to be unique and may actually decrease(see http://wiki.bazaar.canonical.com/Revision). In this case, system will not notice new entries in history of repository.

Redmine should probably use "revision id" instead of "revision number" or (maybe not better, but I think easier and sufficient) date of last commit.

To get revision id and timestamp of last commit you can do:

bzr log --show-ids -r last:1


Related issues

Related to Redmine - Defect #6681: Mercurial, Bazaar and Darcs auto close issue text should be commit id instead of revision numberClosed2010-10-15

Actions
Related to Redmine - Defect #3724: Mercurial repositories display revision ID instead of changeset IDClosedToshi MARUYAMA2009-08-10

Actions
Related to Redmine - Feature #2799: Support for Bazaar's shared reposetories (created with init-repo)New2009-02-21

Actions
Related to Redmine - Defect #7984: Confusing revisions links on repository rootNewToshi MARUYAMA2011-03-24

Actions
Actions #1

Updated by Etienne Massip almost 13 years ago

Is it the same as #6681 ?

Actions #2

Updated by Toshi MARUYAMA almost 13 years ago

Please see #2799.

Actions #3

Updated by Radosław Grzanka almost 13 years ago

Yes, it seems to be related to #6681 but I don't know how it relates to #2799 except that people tries to make bazaar integration better.

I don't have shared repo or some very complicated setup. If two developers branches one repo and work on their copy they both increment revision numbers. Upon merge, it is not guaranteed that revno will be greater then previously in "central" repo - this assumption is wrong.

Actions #4

Updated by Toshi MARUYAMA almost 13 years ago

Trac Hook for Bazaar Repository
http://trac.ultimania.org/trac/bzr-doc-ja/browser/bzr-trac-hook/trunk/README_ja#L71

Japanese:
Tracと連携する場合、Bazaarはappend_revisions_onlyオプションを指定して運用する必要があります。

English:
If you want to work with Trac, Bazaar needs to set append_revisions_only option.

Actions #5

Updated by Toshi MARUYAMA almost 13 years ago

Actions

Also available in: Atom PDF