git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick Steinhardt <ps@pks.im>
To: Jeff King <peff@peff.net>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 1/4] ci: drop run-docker scripts
Date: Thu, 12 Sep 2024 12:40:56 +0200	[thread overview]
Message-ID: <ZuLFODJB3Ak8Y2WK@pks.im> (raw)
In-Reply-To: <20240912094336.GA589828@coredump.intra.peff.net>

On Thu, Sep 12, 2024 at 05:43:36AM -0400, Jeff King wrote:
> We haven't used these scripts since 4a6e4b9602 (CI: remove Travis CI
> support, 2021-11-23), as the GitHub Actions config has support for
> directly running jobs within docker containers.
> 
> It's possible we might want to resurrect something like this in order to
> be more agnostic to the CI platform. But it's not clear exactly what it
> would look like. And in the meantime, it's just a maintenance burden as
> we make changes to CI config, and is subject to bitrot. In fact it's
> already broken; it references ci/install-docker-dependencies.sh, which
> went away in 9cdeb34b96 (ci: merge scripts which install dependencies,
> 2024-04-12).
> 
> Signed-off-by: Jeff King <peff@peff.net>
> ---
> I think this is worth doing even if we don't take the rest of the
> patches. But obviously it gets even more bit-rotted as the other patches
> change the CI config file.

I initially wanted to use them for GitLab CI, but eventually I figured
that it makes way more sense to just merge the setup instructions we
have into a single, unified script. Docker or not doesn't really matter
all that much when you want to install dependencies. What matters more
is the actual platform you're on, but that is independent of Docker
anyway.

The only remaining usecase I could see for these is to run CI-like
builds on a developer's machine. But the fact that these scripts don't
work at all anymore and have started to bitrot already demonstrates that
nobody does seem to do that in the first place.

So I think removing them is the right thing to do.

Patrick

  reply	other threads:[~2024-09-12 10:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 23:00 [PATCH] ci: remove 'Upload failed tests' directories' step from linux32 jobs Junio C Hamano
2024-09-11 22:32 ` Junio C Hamano
2024-09-12  7:56   ` Jeff King
2024-09-12  8:00     ` Jeff King
2024-09-12  9:42       ` [PATCH 0/4] make linux32 ci job work with recent actions Jeff King
2024-09-12  9:43         ` [PATCH 1/4] ci: drop run-docker scripts Jeff King
2024-09-12 10:40           ` Patrick Steinhardt [this message]
2024-09-12  9:45         ` [PATCH 2/4] ci: unify ubuntu and ubuntu32 dependencies Jeff King
2024-09-12 10:41           ` Patrick Steinhardt
2024-09-12  9:47         ` [PATCH 3/4] ci: use more recent linux32 image Jeff King
2024-09-12 10:41           ` Patrick Steinhardt
2024-09-12 11:22             ` Jeff King
2024-09-12 11:53               ` Patrick Steinhardt
2024-09-12 12:47                 ` Patrick Steinhardt
2024-09-13  4:55                   ` Jeff King
2024-09-13  5:39                     ` Patrick Steinhardt
2024-09-12  9:48         ` [PATCH 4/4] ci: use regular action versions for linux32 job Jeff King
2024-09-12 19:41         ` [PATCH 0/4] make linux32 ci job work with recent actions Junio C Hamano
2024-09-13  5:52         ` [PATCH 5/4] ci: add Ubuntu 16.04 job to GitLab CI Patrick Steinhardt
2024-09-13  6:21           ` Jeff King
2024-09-13  6:39             ` Patrick Steinhardt
2024-09-13  6:43               ` Jeff King
2024-09-13  6:47                 ` Patrick Steinhardt
2024-09-13 16:17             ` Junio C Hamano

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=ZuLFODJB3Ak8Y2WK@pks.im \
    --to=ps@pks.im \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    /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;
as well as URLs for NNTP newsgroup(s).