Defect #6371
closed
reposman.rb creates SVN root for GIT one
0%
Description
Hi,
I have encountered issue of reposman.rb when is added a new git repository and reposman.rb is used in cron without --scm option then reposman.rb creates svn root for git repository.
I suggest a solution when in loop of programs would happend a skip (next) when $scm is different than chosen type of repository.. I tried to implement it on my own, but dont know ruby..
Or is there any elegant way to have enabled git,svn,.. for one installation of Redmine and let Redmine/reposman.rb create repo root to a specific dir like /repos/svn, /repos/git respectively for projects separately?
Thanks
Updated by Felix Schäfer over 13 years ago
- Status changed from New to Closed
- Priority changed from High to Normal
- Resolution set to Invalid
The help for reposman clearly states "the kind of SCM repository you want to create (and register) in Redmine (default: Subversion).", i.e. reposman can only be used to create one type of repository globally. Furthermore, reposman will never create a repository if one is already declared for a project (unless @--force@d too), so if you have declared a git repository in one project, reposman won't create a new repository for it, svn or otherwise.
As to multiple SCM support for reposman: the problem is that you currently can't give a role access to the repository configuration project options without giving them full access, essentially nullifying the usefulness of reposman. I think there was a plugin/patch around that would populate the repository options only with a list from which one could choose what repository he wanted to have as well as update reposman to support that, but I'm not sure how up-to-date it is.