Johannes Schindelin 5ed9fc3fc8 ci: prevent perforce from being quarantined ... The most recent Azure Pipelines macOS agents enable what Apple calls "System Integrity Protection". This makes `p4d -V` hang: there is some sort of GUI dialog waiting for the user to acknowledge that the copied binaries are legit and may be executed, but on build agents, there is no user who could acknowledge that. Let's ask Homebrew specifically to _not_ quarantine the Perforce binaries. Helped-by: Aleksandr Chebotov Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>		2020-02-27 09:58:42 -08:00
..
util	travis-ci: include the trash directories of failed tests in the trace log	2018-08-01 09:59:36 -07:00
install-dependencies.sh	ci: prevent perforce from being quarantined	2020-02-27 09:58:42 -08:00
lib.sh	Merge branch 'sg/osx-force-gcc-9'	2019-12-06 15:09:21 -08:00
make-test-artifacts.sh	ci: parallelize testing on Windows	2019-01-29 09:26:47 -08:00
mount-fileshare.sh	Add a build definition for Azure DevOps	2019-01-29 09:26:46 -08:00
print-test-failures.sh	ci/lib.sh: add support for Azure Pipelines	2019-01-29 09:26:46 -08:00
run-build-and-tests.sh	travis-ci: build with GCC 4.8 as well	2019-07-19 14:06:01 -07:00
run-linux32-build.sh	Merge branch 'js/vsts-ci'	2019-02-06 22:05:26 -08:00
run-linux32-docker.sh	ci: rename the library of common functions	2019-01-28 10:34:28 -08:00
run-static-analysis.sh	ci: run hdr-check as part of the Static Analysis job	2019-10-03 10:34:57 +09:00
run-test-slice.sh	ci: parallelize testing on Windows	2019-01-29 09:26:47 -08:00
test-documentation.sh	ci: ignore rubygems warning in the "Documentation" job	2020-02-10 09:52:27 -08:00