From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] CI: remove support for Azure CI
Date: Mon, 20 Dec 2021 18:38:04 +0100 (CET) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2112201834050.347@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <patch-1.1-eec0a8c3164-20211217T000418Z-avarab@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1298 bytes --]
Hi Ævar,
On Fri, 17 Dec 2021, Ævar Arnfjörð Bjarmason wrote:
> Remove various code required to support Azure CI. Recently in
> 4a6e4b96026 (CI: remove Travis CI support, 2021-11-23) we removed the
> Travis CI support, which was last used in June 2021.
>
> The supporting infrastructure for Azure CI was already partially
> removed in 6081d3898fe (ci: retire the Azure Pipelines definition,
> 2020-04-11). As that commit notes:
>
> We have GitHub Actions now. Running the same builds and tests in Azure
> Pipelines would be redundant, and a waste of energy.
>
> This follow-up removes the relevant Azure Pipelines-only supporting
> code. Most of it was added in commits merged as part of
> 57cbc53d3e0 (Merge branch 'js/vsts-ci', 2019-02-06).
It feels premature to remove the remnants of Azure Pipelines support
already now. It would be better to hold off a little, as much fun as
deleting and refactoring code may be for some of us.
The reason is that there are still some things that Azure Pipelines can do
that GitHub workflows cannot, for example:
- present the logs of failed tests in an intuitive manner,
- re-run _only_ failed jobs.
At this stage, I am not convinced yet that we should bet completely on
GitHub workflows.
Ciao,
Johannes
next prev parent reply other threads:[~2021-12-20 17:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 0:04 [PATCH] CI: remove support for Azure CI Ævar Arnfjörð Bjarmason
2021-12-20 17:38 ` Johannes Schindelin [this message]
2021-12-20 18:05 ` Ævar Arnfjörð Bjarmason
2021-12-20 19:08 ` 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=nycvar.QRO.7.76.6.2112201834050.347@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
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).