Project

General

Profile

Actions

Defect #32191

open

Duplicate associated revisions when using multiple repositories for a project

Added by Jon Schell about 5 years ago. Updated about 5 years ago.

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

0%

Estimated time:
Resolution:
Duplicate
Affected version:

Description

I have a project that has several repositories linked to it. Repo A includes an extern to a folder in Repo B. When a commit is made to Repo A the associated issue displays the associated revision entry twice. Both are identical. When a commit is made to Repo B, it's done correctly with a single entry. The commits are not spanning the repos over the extern, they are entirely within one repo or the other.

Attached picture shows the first entry only once because it's done to Repo B. The rest are commits to Repo A.

We do have the option to fetch commits automatically turned off and instead we run a cron job using "redmine:fetch_changesets" to update it.

Database manager version: Mysql2
Ruby version: 2.1.5-p273 (2014-11-13) [x86_64-linux-gnu]
Rails version: 4.2.8
Redmine version: 3.4.3.stable
scm binary version: svn 1.8.10
No plugins


Files

Capture.PNG (106 KB) Capture.PNG Jon Schell, 2019-10-04 02:20

Related issues

Is duplicate of Redmine - Defect #6857: git references leaking from subproject to projectNew2010-11-09

Actions
Actions #1

Updated by Go MAEDA about 5 years ago

  • Status changed from New to Closed
  • Resolution set to Duplicate

The issue is known as #6857 but has not fixed yet. Thank you for reporting the issue you found.

Actions #2

Updated by Go MAEDA about 5 years ago

  • Is duplicate of Defect #6857: git references leaking from subproject to project added
Actions #3

Updated by Mischa The Evil about 5 years ago

Go MAEDA wrote:

The issue is known as #6857 [...]

That was my first thought too, but then I carefully re-read the (brief) description given by the OP. It explicitly states that they are using multiple (svn) repos per project along with svn externals pointing to parts of the other linked repos. It says nothing about the use of subprojects.

Based on that I don't see how this issue is known as #6857. I rather think that this is a more complex issue which has to do with the svn externals feature, and possibly in combination with the multiple repo feature of Redmine.
What do you think?

Actions #4

Updated by Go MAEDA about 5 years ago

  • Status changed from Closed to New
Actions #5

Updated by Jon Schell about 5 years ago

Yes, we have no sub-projects. It looks like comment #7 on #6857 is similar, so this problem likely has been around a while. I tried looking at the source code and didn't see anything obvious that would explain it.

Actions

Also available in: Atom PDF