Project

General

Profile

Actions

Feature #30854

closed

git 2.17 compatibility

Added by Cliff Ingham about 5 years ago. Updated about 5 years ago.

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

0%

Estimated time:
Resolution:
Invalid

Description

When trying to add an existing git repository to redmine, we get the error:

Path to repository is invalid

I think this is because our newer git repositories were created using git 2.17. We can successfully add git repositories that were created with prior versions of git. It would be nice to have support for git repositories created with git 2.17.


Files

debug.log (1.38 KB) debug.log Debug Log Output Cliff Ingham, 2019-02-21 20:59
Actions #1

Updated by Cliff Ingham about 5 years ago

I've attached the relevant portion from the debug log. It looks like it is complaining that the repository already exists. However, when I go into mysql, and do a select for all the repositories, the one I'm trying to create does not exist.

Actions #2

Updated by Cliff Ingham about 5 years ago

After debugging some more, it turns out the regexp for valid GIT repository urls does not allow periods in the repository name. So, the Github naming scheme is not valid.

Validating /srv/git/kubernetes.git
Using regexp: file:///srv/git/[a-z0-9_]+

It seems like the regexp should allow periods in the url.

Actions #3

Updated by Cliff Ingham about 5 years ago

  • Status changed from New to Resolved

Okay, so it turns out I was just very confused. This was all because of our the invalid regexp in our configuration.yml.

Redmine was correctly applying the path regexp that we had declared in our configuration.yml.

Actions #4

Updated by Holger Just about 5 years ago

  • Status changed from Resolved to Closed
  • Resolution set to Invalid
Actions

Also available in: Atom PDF