summaryrefslogtreecommitdiff
path: root/t/t1404-update-ref-errors.sh
diff options
context:
space:
mode:
authorLibravatar Johannes Schindelin <johannes.schindelin@gmx.de>2021-10-13 12:55:48 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2021-10-13 10:36:17 -0700
commit7491ef619844ff2a47f962e1ad83ef163f9c9b38 (patch)
tree5bf5f10eed332367a3aa50ee74e6bc39a569e41e /t/t1404-update-ref-errors.sh
parentGit 2.33.1 (diff)
downloadtgif-7491ef619844ff2a47f962e1ad83ef163f9c9b38.tar.xz
ci(windows): ensure that we do not pick up random executables
On the Windows build agents, a lot of programs are installed, and added to the PATH automatically. One such program is Git for Windows, and due to the way it is set up, unfortunately its copy of `gpg.exe` is also reachable via the PATH. This usually does not pose any problems. To the contrary, it even allows us to test the GPG parts of Git's test suite even if `gpg.exe` is not delivered as part of `git-sdk-64-minimal`, the minimal subset of Git for Windows' SDK that we use in the CI builds to compile Git. However, every once in a while we build a new MSYS2 runtime, which means that there is a mismatch between the copy in `git-sdk-64-minimal` and the copy in C:\Program Files\Git\usr\bin. When that happens we hit the dreaded problem where only one `msys-2.0.dll` is expected to be in the PATH, and things start to fail. Let's avoid all of this by restricting the PATH to the minimal set. This is actually done by `git-sdk-64-minimal`'s `/etc/profile`, and we just have to source this file manually (one would expect that it is sourced automatically, but the Bash steps in Azure Pipelines/GitHub workflows are explicitly run using `--noprofile`, hence the need for doing this explicitly). Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t1404-update-ref-errors.sh')
0 files changed, 0 insertions, 0 deletions