ci: add ci-artifacts pipeline

[dennisameling]

This is step 3 of configuring ci-artifacts pipelines to upload artifacts to GitHub releases.

A similar pipeline already exists in git-sdk-64, so this commit is to port most of that code to git-sdk-arm64.

We don't (yet) copy over the test-minimal-sdk job, because it spins up 16 parallel jobs, which is probably a bit too much for our self-hosted runner budget. We can add those once GitHub-hosted arm64 runners become available for OSS projects by the end of 2024.

[dscho]

So you don't want to have those 20 test-minimal-sdk matrix jobs? 😁

Even so, it may make sense to at least clone git/git and build it, without compressing and uploading git-artifacts.tar.gz, just to make sure that it can be built.

Besides, if you leave out that big matrix job, what remains is a sequence of 3 jobs that have to be run in order, all on Windows/ARM64. That's a bit wasteful what with spinning up and tearing down VMs, it would probably make sense to merge them into a single job (and then the upload-artifact/download-artifact steps become unnecessary).

The rest of the diff relative to git-for-windows#87 version of the workflow looks reasonable to me. Thank you so much!

[dennisameling]

So you don't want to have those 20 test-minimal-sdk matrix jobs? 😁

I'd love to have those, but your Azure subscription wouldn't really like that. I keep running into a concurrent cores quota when running multiple things in parallel. I should have clarified that a bit more in the PR description. Happy to add those right away once the Hosted ARM64 Runners are in place, which also start within just a few seconds in my testing 😄

Besides, if you leave out that big matrix job, what remains is a sequence of 3 jobs that have to be run in order, all on Windows/ARM64. That's a bit wasteful what with spinning up and tearing down VMs, it would probably make sense to merge them into a single job (and then the upload-artifact/download-artifact steps become unnecessary).

The third one was ubuntu-latest actually, but agreed, let's merge them!

I just kicked off a pipeline in my fork, and everything's working as expected 🎉 Here's the release with the artifacts.

@dscho shall we kill my TO-DROP commit and get this merged? 😊

[dscho]

So you don't want to have those 20 test-minimal-sdk matrix jobs? 😁

I'd love to have those, but your Azure subscription wouldn't really like that.

😀 Thank you for being considerate!

I keep running into a concurrent cores quota when running multiple things in parallel. I should have clarified that a bit more in the PR description. Happy to add those right away once the Hosted ARM64 Runners are in place, which also start within just a few seconds in my testing 😄

Yes, I bet! All the more sad that hosted Windows/ARM64 runners are still not free for OSS. I could imagine that this is part of the reason why the ecosystem is so slow to support Windows/ARM64. It sure holds me back.

I just kicked off a pipeline in my fork, and everything's working as expected 🎉 Here's the release with the artifacts.

@dscho shall we kill my TO-DROP commit and get this merged? 😊

Awesome, let's do that!

[dscho]

@dennisameling oy vey, I forgot that git-sdk-arm64 is a fork of git-sdk-64!

[dscho]

See https://github.com/git-for-windows/git-sdk-arm64:

So maybe we want to imitate this:

    if: github.repository_owner == 'git-for-windows'

@dennisameling what do you think?

[dennisameling]

So maybe we want to imitate this:

    if: github.repository_owner == 'git-for-windows'

@dennisameling what do you think?

Sounds good, was going to suggest something similar. Do you want to push a commit to main, or want me to do it?

[dscho]

@dennisameling please go ahead, I am busy with some Git for Windows patches in preparation for the upcoming release.

[dennisameling]

Looks like that worked! The self-hosted runner is still being created; I'll keep an eye on it.