"Johannes Schindelin via GitGitGadget" <gitgitgadget@xxxxxxxxx> 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?). 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). 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 ;-) Thanks.
