[gmx-developers] Transition to Gitlab

[Erik Lindahl]

Hi,

I have no strong feelings, since as you say there are pros/cons to both work flows.

What I do like with gitlab is the (very) strong integration with CI, and that we csn trivially have gitlab-runner work in our own infrastructure - but control all the actual test runs directly as image/command specifications in a dot file.

To me, that seems like something that would completely get rid of the most boring and difficult/undocument parts of our current setup, and the CI setup would just be part of our normal code check-ins.

So, without discounting hosted Gerrit, or whether we prefer one code review setup or another, I think it's important that we consider the entire work flow and how to minimize the amount of administration required.

Cheers,

Erik

Erik Lindahl <erik.lindahl at scilifelab.se>
Professor of Biophysics
Science for Life Laboratory
Stockholm University & KTH
Office (SciLifeLab): +46 8 524 81567
Cell (Sweden): +46 73 4618050
Cell (US): +1 (650) 924 7674 



> On 31 Jul 2019, at 23:30, Berk Hess <hess at kth.se> wrote:
> 
> That's important information.
> 
> Is there some place which discusses the pros and cons of both workflows?
> 
> Cheers,
> 
> Berk
> 
>> On 7/31/19 11:09 PM, Schulz, Roland wrote:
>> How will the code review work in gitlab? We are planning to switch to the pull-request workflow from the current gerrit workflow? They both have pros and cons but they are very different. So I think that's an important decision. And note that you really need to change to the different best practices for a pull-request workflow. Github/gitlab don't work well if you rebase changes which is required for gerrit.
>> Note that http://www.gerritforge.com/pricing.html#platinum provides free Gerrit hosting for OpenSource projects. So if we want to stick with the gerrit forkflow we can do so while moving to a hosted solution. But gerritforge only works with github and not gitlab. So it wouldn't make sense to move the issues to gitlab if we wanted to use gerritforge.
>> 
>> Roland
>> 
>>> -----Original Message-----
>>> From: gromacs.org_gmx-developers-bounces at maillist.sys.kth.se
>>> [mailto:gromacs.org_gmx-developers-bounces at maillist.sys.kth.se] On
>>> Behalf Of Paul bauer
>>> Sent: Wednesday, July 31, 2019 8:45 AM
>>> To: gromacs.org_gmx-developers at maillist.sys.kth.se
>>> Subject: [gmx-developers] Transition to Gitlab
>>> 
>>> Hello @ all developers,
>>> 
>>> the core team is currently investigating a transition of our code review, issue
>>> tracking and CI to Gitlab, to reduce the time developers need to spend on
>>> maintaining our current, self-hosted infrastructure.
>>> As part of this we are planning to transfer the information in Redmine to
>>> Gitlab issues and milestones.
>>> 
>>> We want to have issues and such still linked to the correct users/developers,
>>> so we need the Gitlab user names of those of you that are interested to
>>> continue development on Gitlab.
>>> This is a requirement of the script that performs the transition :( Those users
>>> should also link themselves to the GROMACS organisation
>>> (https://gitlab.com/gromacs).
>>> 
>>> Please send the Gitlab user names as private e-Mail to either me or another
>>> member of the core team.
>>> 
>>> Cheers
>>> 
>>> Paul
>>> 
>>> 
>>> --
>>> Paul Bauer, PhD
>>> GROMACS Release Manager
>>> KTH Stockholm, SciLifeLab
>>> 0046737308594
> 
> -- 
> Gromacs Developers mailing list
> 
> * Please search the archive at http://www.gromacs.org/Support/Mailing_Lists/GMX-developers_List before posting!
> 
> * Can't post? Read http://www.gromacs.org/Support/Mailing_Lists
> 
> * For (un)subscribe requests visit
> https://maillist.sys.kth.se/mailman/listinfo/gromacs.org_gmx-developers or send a mail to gmx-developers-request at gromacs.org.