[gmx-developers] Switching Infrastructure to Gitlab

Paul bauer paul.bauer.q at gmail.com
Tue Mar 24 06:44:14 CET 2020

Hello and good morning again,

there will be some more downtime than expected, because the transfer of 
issues to Gitlab crashed over night.
Also, I'll need to rename the current GROMACS project to something else, 
as the Gitlab API does not allow renumbering issues and I would have to 
upload the issues again starting at the point of the crash this night.
To make sure numbers make sense, I'll create a new project, upload the 
database there (hopefully now in one go), upload the repository to it, 
change the current GROMACS project to GROMACS-mirror, and then move the 
new project back to GROMACS.

If this sounds convoluted I have to agree it is, but this seems to be 
the only way.

Will get back to you again later once I'm done.



On 23/03/2020 21:26, Paul bauer wrote:
> Hello again,
> just a quick heads up that I had to move the project on Gitlab to 
> private for the duration of the transfer and will move it back to 
> public as soon as the redmine database has been transferred.
> Cheers
> Paul
> On 23/03/2020 14:00, Paul bauer wrote:
>> Hello gmx developers,
>> I will be switching the gerrit.gromacs.org and redmine.gromacs.org 
>> servers to read only now to begin the transfer of the Redmine 
>> database to Gitlab, and to allow us to switch the Gitlab repository 
>> from being a mirror of git.gromacs.org to the source of it.
>> As part of this there will be some downtime until we have transferred 
>> everything, but I think this will be resolved before tomorrow morning.
>> I'll let you know when the process is done and the issues have been 
>> transferred, and when the Gitlab repository is set to accept new 
>> patches.
>> Hope you are all doing well, and see you soon on Gitlab!
>> Cheers
>> Paul

Paul Bauer, PhD
GROMACS Development Manager
KTH Stockholm, SciLifeLab

More information about the gromacs.org_gmx-developers mailing list