git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Olliver Schinagl <oliver@schinagl.nl>
Cc: git@vger.kernel.org, gitster@pobox.com,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	psteinhardt@gitlab.com
Subject: Re: Git mirror at gitlab
Date: Thu, 21 Dec 2023 12:48:12 +0100	[thread overview]
Message-ID: <ZYQl_G-S4vQibHWn@framework> (raw)
In-Reply-To: <2a833bfc-a075-4e78-ae6c-270f5198d498@schinagl.nl>

[-- Attachment #1: Type: text/plain, Size: 3239 bytes --]

On Thu, Dec 21, 2023 at 12:30:02PM +0100, Olliver Schinagl wrote:
> Hey list,
> 
> For years, I wanted (tried, but time) to run the mirror for git on gitlab.
> Actually, the original idea was to run a docker container ([0] 10k+ pulls
> :p)
> 
> I initially set this up via docker build containers, where docker hub would
> pull my mirror of the git repo. My mirror, because I added a Dockerfile
> which was enough for docker to do its trick. I was planning (time ..) on
> submitting this upstream to the list, but never did. Because of me not doing
> that, I had to manually (I was even too lazy to script it) rebase the
> branch. Docker then did some changes to their business, where the docker
> builds where not possible anymore.
> 
> So then I figured, I'll do the same on gitlab and push it to the docker hub.
> Thus I setup a mirror on gitlab [1], with the idea to work there on it.
> 
> Again, I never got around to finalize this work, mostly because the docker
> container 'just worked' for pretty much everything. After all, git is very
> stable overal.
> 
> So very interestingly, last month commit 0e3b67e2aa25edb ("ci: add support
> for GitLab CI") landed, which started to trigger pipeline jobs!
> 
> Sadly, this only worked for 3 builds, as that's when the minutes ran out :)
> 
> So one, I would very much like to offer the registered names (cause they are
> pretty nice in name) to here, so people can use and find it.

Not to throw a wrench into this, but are you aware of the official
GitLab mirror at https://gitlab.com/git-vcs/git? I myself wasn't aware
of this mirror for a rather long time.

I also wondered whether we want to have https://gitlab.com/git/git as we
do on GitHub. I don't think anybody registered it, but it is blocked
from being registered as far as I can tell. Maybe we block the namespace
out of caution, I dunno. I can certainly check in with our SREs in case
it is something the Git project would like to own.

> Two, hopefully get Patrick Steinhardt to help out to get unlimited minutes
> and storage on the repo :)

I'm sure we can do something here, but I'd rather aim to do this for the
official mirror which currently is the one I mentioned above. If the
project is interested in running builds on GitLab then I'm happy to
coordinate.

Also Cc Ævar, who is the current owner of the mirror. Would it be
possible to add myself as a second owner to the project? This might help
setting up the CI infrastructure. But please, if anybody disagrees with
me being added as an owner here I encourage you to say so.

> Three, see what the opinion of people here is on this. I'll do the work to
> get the dockerfile (now containerfile, we're inclusive after all) merged,
> and the CI file updated to create, store (and push to docker hub) the
> generated containers.

I don't really have much of an opinion here and will leave it to others
to discuss.

Thanks!

Patrick

PS: As most other folks I'll be OOO during holidays, so I may only
    answer sporadically.

> Thanks,
> Olliver
> 
> [0]: https://hub.docker.com/r/gitscm/git
> [1]: https://gitlab.com/gitscm/git
> 
> P.S. I'm not subscribed, so please keep me in the CC :)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2023-12-21 11:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-21 11:30 Git mirror at gitlab Olliver Schinagl
2023-12-21 11:48 ` Patrick Steinhardt [this message]
2023-12-22 14:06   ` Olliver Schinagl
2023-12-28 11:13     ` Patrick Steinhardt
2023-12-28 14:50       ` Phillip Wood
2024-01-17  6:35   ` Patrick Steinhardt
2024-03-21 11:24     ` Patrick Steinhardt
2024-03-21 16:34       ` Junio C Hamano
2024-03-21 22:27         ` Olliver Schinagl
2024-03-22  0:44           ` Patrick Steinhardt
2024-03-22 10:08             ` Christian Couder
2024-03-22 13:04               ` Patrick Steinhardt
2024-03-29 14:47                 ` [PATCH 1/2] cook: switch unmaintained GitLab mirror to new URL Patrick Steinhardt
2024-03-29 18:11                   ` Junio C Hamano
2024-03-29 14:47                 ` [PATCH 2/2] cook: update mirror URLs to use HTTPS Patrick Steinhardt
2024-03-30  8:14                 ` Git mirror at gitlab Olliver Schinagl
2024-03-30  8:18                   ` Patrick Steinhardt
2024-03-30  8:20                     ` Olliver Schinagl
2024-03-30  9:06                       ` Patrick Steinhardt
2024-03-30 10:59                         ` Olliver Schinagl
2024-03-30 18:06                           ` Patrick Steinhardt
2024-03-30 23:54                             ` Olliver Schinagl
2024-03-31  7:26                               ` Patrick Steinhardt

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ZYQl_G-S4vQibHWn@framework \
    --to=ps@pks.im \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=oliver@schinagl.nl \
    --cc=psteinhardt@gitlab.com \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).