91839a8827
In order to build and test Git, we have to first set up the Git for Windows SDK, which contains various required tools and libraries. The SDK is basically a clone of [1], but that repository is quite large due to all the binaries it contains. We thus use both shallow clones and sparse checkouts to speed up the setup. To handle this complexity we use a GitHub action that is hosted externally at [2]. Unfortunately, this makes it rather hard to reuse the logic for CI platforms other than GitHub Actions. After chatting with Johannes Schindelin we came to the conclusion that it would be nice if the Git for Windows SDK would regularly publish releases that one can easily download and extract, thus moving all of the complexity into that single step. Like this, all that a CI job needs to do is to fetch and extract the resulting archive. This published release comes in the form of a new "ci-artifacts" tag that gets updated regularly [3]. Implement a new script that knows how to fetch and extract that script and convert GitHub Actions to use it. [1]: https://github.com/git-for-windows/git-sdk-64/ [2]: https://github.com/git-for-windows/setup-git-for-windows-sdk/ [3]: https://github.com/git-for-windows/git-sdk-64/releases/tag/ci-artifacts/ Helped-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Patrick Steinhardt <ps@pks.im> Signed-off-by: Junio C Hamano <gitster@pobox.com>
13 lines
478 B
PowerShell
Executable File
13 lines
478 B
PowerShell
Executable File
param(
|
|
[string]$directory='git-sdk',
|
|
[string]$url='https://github.com/git-for-windows/git-sdk-64/releases/download/ci-artifacts/git-sdk-x86_64-minimal.zip'
|
|
)
|
|
|
|
Invoke-WebRequest "$url" -OutFile git-sdk.zip
|
|
Expand-Archive -LiteralPath git-sdk.zip -DestinationPath "$directory"
|
|
Remove-Item -Path git-sdk.zip
|
|
|
|
New-Item -Path .git/info -ItemType Directory -Force
|
|
New-Item -Path .git/info/exclude -ItemType File -Force
|
|
Add-Content -Path .git/info/exclude -Value "/$directory"
|