From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [IMPORTANT] gitlab relocation / rename
Date: Wed, 24 Feb 2021 09:30:58 +0100 [thread overview]
Message-ID: <621240.1614155458@gemini.denx.de> (raw)
Hi all,
I'm sorry that I have to inform you about a disruption of the gitlab
services. This has become necessary for a number of reasons:
- repeated cases of poor performance
- difficulties with CI setup
- security issues
We have to move all public projects off gitlab.denx.de to a new
gitlab instance; the new host name is then source.denx.de .
We are fully aware that this will cause inconveniences, and I can
only assure you that we try hard to keep these as limited as
possible.
# Details
Around noon on Saturday, 2021-02-27, we will freeze all public
repositories on gitlab.denx.de. They will still be readable/
cloneable but any attempt to push new commits after this point will
fail.
We will then copy them over to the now host, source.denx.de .
All custodian accounts will also be transferred, the same login
credentials from gitlab.denx.de will work on source.denx.de .
The URLs for the repositories will stay the same, except of course
for the host name. So, for example, the U-Boot mainline repository
will then be hosted at
https://source.denx.de/u-boot/u-boot.git
We will install redirects to forward HTTP accesses from the old
repository URLs to the new host. This should make the transition
mostly transparent, but does not cover everything. The following
needs to be taken care of manually:
- Update the SSH URI for pushing to the repositories. Just replace
gitlab.denx.de with source.denx.de . We will transfer all the
SSH-keys to the new host so nothing else should be needed.
- Make sure you're logging in on source.denx.de . Access to
gitlab.denx.de will no longer work!
- CI runners connected to gitlab.denx.de need to be re-registered
with source.denx.de .
The new host should hopefully be operational sometime on Sunday,
2021-02-28. We will send a further announcement once everything is
back up and running.
Thanks for your understanding and patience!
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
At the source of every error which is blamed on the computer you will
find at least two human errors, including the error of blaming it on
the computer.
next reply other threads:[~2021-02-24 8:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 8:30 Wolfgang Denk [this message]
2021-02-28 15:14 ` [IMPORTANT] gitlab relocation / rename Wolfgang Denk
2021-03-08 7:34 ` Henning Schild
2021-03-10 7:56 ` Wolfgang Denk
2021-03-10 11:31 ` Henning Schild
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=621240.1614155458@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox