I'm looking for a part-time remote job.

Hire me


I'm the author of:

Mastering Redmine is a comprehensive guide with tips, tricks and best practices, and an easy-to-learn structure.

Check the book's project or

Buy the book

Social pages of the book:

By buying this book you also donate to Redmine (see this page).


Follow me:

Feature #1690

Repository name should be identical to project identifier

Added by Andriy Lesyuk about 13 years ago. Updated almost 13 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
26 Mar 2011
Due date:
28 May 2011
% Done:

100%

External issue:

Description

The “Subversion creator” plugin works cool along with Redmine based authentication (implemented by perl module Redmine.pm). But the last has a limitation - repository name must be identical to project identifier (source):

If the repositories are not created automatically by reposman.rb, it is important that the repository name is the same as the project identifier in Redmine, otherwise Redmine.pm will fail to authenticate users. For example, if the path to the repository is /path/to/repository/foo-bar, then the project Identifier on the Settings page must be foo-bar.

The plugin should take into account this... For now I have two suggestions:
  1. Instead of just SVN root directory the plugin could use full repository path (with project identifier) when filling in repository URL (so users would just need to “accept” URL);
  2. Patch Redmine.pm to support different repository name.

History

#1 Updated by Andriy Lesyuk almost 13 years ago

  • Target version set to 0.1.0

#2 Updated by Andriy Lesyuk almost 13 years ago

  • Status changed from Open to In Progress
  • Assignee set to Andriy Lesyuk
  • % Done changed from 0 to 50

Using project identifier as well... Not patching Redmine.pm for now.

#3 Updated by Andriy Lesyuk almost 13 years ago

Now the plugin suggests project identifier as repository name... Maybe it should print some warning if user chooses a different name?.. If not the issue can be closed.

#4 Updated by Andriy Lesyuk almost 13 years ago

  • Due date set to 28 May 2011
  • Status changed from In Progress to Closed
  • % Done changed from 50 to 100

Writing warning...

Also available in: Atom PDF

Terms of use | Privacy policy