Re: [PATCH] ci: avoid pounding on the poor ci-artifacts container

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: May 15, 2020, 13:59 UTC
Message-ID: <nycvar.QRO.7.76.6.2005151557130.55@tvgsbejvaqbjf.bet>
In-Reply-To: <xmqqimh0afkh.fsf@gitster.c.googlers.com>

Hi Junio,

On Tue, 12 May 2020, Junio C Hamano wrote:

Show 15 quoted lines

> "Johannes Schindelin via GitGitGadget" <gitgitgadget@gmail.com>
> writes:
>
> > Let's switch back to using the Build Artifacts of our trusty Azure
> > Pipeline for the time being.
> >
> > To avoid unnecessary hammering of the Azure Pipeline artifacts, we use
> > the GitHub Action `actions/upload-artifact` in the `windows-build` job
> > and the GitHub Action `actions/download-artifact` in the `windows-test`
> > and `vs-test` jobs (the latter now depends on `windows-build` for that
> > reason, too).
>
> I guess this answers a question I sent earlier to the list (our
> mails almost crossed, I guess, as two of us were looking at the same
> problem at around the same time?).

I am terribly sorry, but I did not get to read the Git mailing list at all this week (or for that matter, my private mail). So I would not even have seen your message... :-(

> Hopefully when cmake-for-windows-build topic lands, this can go away
> altogether, but that is probably at least 8 weeks away (3 weeks
> remaining before the next cycle opens, plus a half of 10 week per
> cycle for a typical major release).

The `cmake-for-windows-build` would address only the build part for Visual Studio. The regular Windows build, as well as the parallelized tests _still_ need the `git-sdk-64-minimal` artifact. With or without CMake. That's because neither CMake nor Visual Studio can accommodate the fact that our test suite is implemented in shell script _and_ requires a working Perl interpreter.

> Today's final integration (these days I'm pushing out twice or three
> times a day) contains this one, and it seems to have passed ;-)

Excellent!

Thanks, Dscho