From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin via GitGitGadget <gitgitgadget@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] ci: avoid pounding on the poor ci-artifacts container
Date: Fri, 15 May 2020 15:59:42 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.2005151557130.55@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <xmqqimh0afkh.fsf@gitster.c.googlers.com>
Hi Junio,
On Tue, 12 May 2020, Junio C Hamano wrote:
> "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
next prev parent reply other threads:[~2020-05-15 14:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-12 20:47 [PATCH] ci: avoid pounding on the poor ci-artifacts container Johannes Schindelin via GitGitGadget
2020-05-12 23:39 ` Junio C Hamano
2020-05-15 13:59 ` Johannes Schindelin [this message]
2020-05-13 12:44 ` Đoàn Trần Công Danh
2020-05-15 14:01 ` Johannes Schindelin
2020-05-15 7:55 ` [PATCH v2] " Johannes Schindelin via GitGitGadget
2020-05-15 15:09 ` Junio C Hamano
2020-05-15 21:35 ` Johannes Schindelin
2020-05-15 21:38 ` 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
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=nycvar.QRO.7.76.6.2005151557130.55@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--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.
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).