common-lisp.net GitLab deployment and migration completed successfully
common-lisp.net has successfully deployed GitLab and migrated users, groups, group-memberships and the existing publicly visible git repositories to it. Redirection rules for git access, gitweb and trac have been established and tested. In the migration, we created 390 users, 434 gitlab groups (=projects) and 210 gitlab projects (= git repositories). Should you experience problems, please discuss on clo-devel@common-lisp.net or report to admin@common-lisp.net. Repositories are no longer available under their original locations. Repositories which *are* still in their original locations, have not been migrated to GitLab. The code to seed the system, was written in Common Lisp. In order to do so, we wrote a (minimal) web binding for GitLab's web API. The sources are in a Mercurial repository available at https://common-lisp.net/~ehuelsmann/cl-gitlab and will be moved to https://gitlab.common-lisp.net/cl-gitlab shortly. We hope you enjoy our improved user experience! -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
good afternoon; cl-xml and de-setf-graphics have as yet just a group, but no project. On 2015-03-20, at 11:59, Erik Huelsmann <ehuels@gmail.com> wrote:
common-lisp.net has successfully deployed GitLab and migrated users, groups, group-memberships and the existing publicly visible git repositories to it. Redirection rules for git access, gitweb and trac have been established and tested.
In the migration, we created 390 users, 434 gitlab groups (=projects) and 210 gitlab projects (= git repositories).
Should you experience problems, please discuss on clo-devel@common-lisp.net or report to admin@common-lisp.net.
Repositories are no longer available under their original locations. Repositories which *are* still in their original locations, have not been migrated to GitLab.
The code to seed the system, was written in Common Lisp. In order to do so, we wrote a (minimal) web binding for GitLab's web API. The sources are in a Mercurial repository available at https://common-lisp.net/~ehuelsmann/cl-gitlab and will be moved to https://gitlab.common-lisp.net/cl-gitlab shortly.
We hope you enjoy our improved user experience!
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi James, On Fri, Mar 20, 2015 at 12:28 PM, james anderson <james.anderson@setf.de> wrote:
good afternoon;
cl-xml and de-setf-graphics have as yet just a group, but no project.
That's to be expected: these projects have no associated git projects at the moment. However, to prevent name collisions, we have created groups for all projects on the common-lisp.net system. If you would like, you can migrate the Subversion repositories to GitLab. There's no need to, though, because Subversion will remain a supported version control system. If you still want to migrate, but need help, we can discuss the steps here on clo-devel. Regards, Erik.
good afternoon; On 2015-03-20, at 13:40, Erik Huelsmann <ehuels@gmail.com> wrote:
Hi James,
On Fri, Mar 20, 2015 at 12:28 PM, james anderson <james.anderson@setf.de> wrote: good afternoon;
cl-xml and de-setf-graphics have as yet just a group, but no project.
That's to be expected: these projects have no associated git projects at the moment. However, to prevent name collisions, we have created groups for all projects on the common-lisp.net system.
If you would like, you can migrate the Subversion repositories to GitLab. There's no need to, though, because Subversion will remain a supported version control system. If you still want to migrate, but need help, we can discuss the steps here on clo-devel.
is there a mechanism for the case where it would be best to synchronise them with the github repositories? regards, from berlin,
Hi James,
If you would like, you can migrate the Subversion repositories to GitLab. There's no need to, though, because Subversion will remain a supported version control system. If you still want to migrate, but need help, we can discuss the steps here on clo-devel.
is there a mechanism for the case where it would be best to synchronise them with the github repositories?
Sure! Just file the request with the admins :-) Which Github repositories do you want mirrored exactly? Does this mean that the existing Subversion and CVS repositories on common-lisp.net should be regarded as superseeded? [And can they/should they be removed because of it?] -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
good afternoon erik, On 2015-03-20, at 14:34, Erik Huelsmann <ehuels@gmail.com> wrote:
Hi James,
If you would like, you can migrate the Subversion repositories to GitLab. There's no need to, though, because Subversion will remain a supported version control system. If you still want to migrate, but need help, we can discuss the steps here on clo-devel.
is there a mechanism for the case where it would be best to synchronise them with the github repositories?
Sure! Just file the request with the admins :-) Which Github repositories do you want mirrored exactly?
all three of the projects which you have apportioned to my control are maintained at github https://github.com/lisp/de.setf.amqp https://github.com/lisp/de.setf.graphics https://github.com/lisp/de.setf.xml
Does this mean that the existing Subversion and CVS repositories on common-lisp.net should be regarded as superseeded?
yes.
[And can they/should they be removed because of it?]
as far as i know, there is no reason to retain them. best regards, from berlin,
Hi James,
Sure! Just file the request with the admins :-) Which Github repositories do you want mirrored exactly?
all three of the projects which you have apportioned to my control are maintained at github
https://github.com/lisp/de.setf.amqp https://github.com/lisp/de.setf.graphics https://github.com/lisp/de.setf.xm <https://github.com/lisp/de.setf.xml>l
Ok. These mirrors have been set up. The project de-setf-amqp has 2 repositories now, one called 'git.git' the other is the mirror I set up from github. Do you want me to delete the 'git.git' repository?
Does this mean that the existing Subversion and CVS repositories on common-lisp.net should be regarded as superseeded? yes.
[And can they/should they be removed because of it?] as far as i know, there is no reason to retain them.
Ok. Removed. -- Bye, Erik. http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
Hi Eric, Congratulations for the successful migration :)
common-lisp.net has successfully deployed GitLab and migrated users, groups, group-memberships and the existing publicly visible git repositories to it. Redirection rules for git access, gitweb and trac have been established and tested.
In the migration, we created 390 users, 434 gitlab groups (=projects) and 210 gitlab projects (= git repositories).
Should you experience problems, please discuss on clo-devel@common-lisp.net or report to admin@common-lisp.net.
Repositories are no longer available under their original locations. Repositories which *are* still in their original locations, have not been migrated to GitLab.
The code to seed the system, was written in Common Lisp. In order to do so, we wrote a (minimal) web binding for GitLab's web API. The sources are in a Mercurial repository available at https://common-lisp.net/~ehuelsmann/cl-gitlab and will be moved to https://gitlab.common-lisp.net/cl-gitlab shortly.
We hope you enjoy our improved user experience!
-- Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP. Robust and Flexible. No vendor lock-in.
-- Stelian Ionescu a.k.a. fe[nl]ix Quidquid latine dictum sit, altum videtur. http://common-lisp.net/project/iolib
participants (3)
-
Erik Huelsmann -
james anderson -
Stelian Ionescu