As part of our continuing push to make GCE a full service computing environment for our researchers, and to get to our goal of retiring old and outdated servers and services, we’re delighted to announce that our new Gitlab service in GCE is now live.
Server: git.cels.anl.gov Documentation: virtualhelpdesk.cels.anl.gov/docs/service-catalog/developer-and-collaboration-tools-and-services/gitlab/
This new server is set up much as the existing servers are, but with more of an eye towards CI/CD workflows. We do not yet have Pages functionality ready, but it’s on the roadmap and will be announced when it’s good to go. I didn’t want to block on that function, and it’s not one our existing servers are providing.
The old servers are running on end-of-life operating systems and we will need to retire those in the not-too-distant future. Luckily, migrating from one git server to another isn’t too painful. We’ve written up docs on the process at virtualhelpdesk.cels.anl.gov/docs/migrating-from-legacy-to-gce/gitlab/ that walks through the process, but here are the most important bits.
– The migration needs to be done by the project owner. – The email addresses on the old and new server need to match prior to migration. – New external xgitlab accounts will not be processed after January 31, 2021. – New projects will not be able to be created on the legacy servers after February 15, 2021. – The migrations need to be complete by March 30, 2021.
The above migration instructions include the steps your contributors will need to complete to ensure their account is set up on git.cels.anl.gov before the migration happens, and the steps you as a project owner will need to perform to handle the migration.
Those dates are more aggressive than I would have liked, but it took us longer than planned to have the new server ready. If you need assistance with this, please reach out to us at email@example.com<mailto:firstname.lastname@example.org>. I should be clear, the reason the project owners need to drive the migration of their project is due to how the ownership works. If we do it for you, we own the project’s history.
If you’re currently using any of our subversion servers and are open to moving to git, please reach out and we’ll help you. There will be more communications like this as new services in GCE roll out and older services in Legacy reach end of life.