summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJohannes Schindelin <johannes.schindelin@gmx.de>2020-02-27 13:23:12 (GMT)
committerJunio C Hamano <gitster@pobox.com>2020-02-27 17:58:42 (GMT)
commit5ed9fc3fc8629d9c13b6bae03a32e28cf8be3e96 (patch)
tree946a8cab8099a916f1b9f495044b3e8fc19c3263
parenteafff6e41e6a16c23764dcd31373bedd61572cf1 (diff)
downloadgit-5ed9fc3fc8629d9c13b6bae03a32e28cf8be3e96.zip
git-5ed9fc3fc8629d9c13b6bae03a32e28cf8be3e96.tar.gz
git-5ed9fc3fc8629d9c13b6bae03a32e28cf8be3e96.tar.bz2
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>
-rwxr-xr-xci/install-dependencies.sh4
1 files changed, 2 insertions, 2 deletions
diff --git a/ci/install-dependencies.sh b/ci/install-dependencies.sh
index cd59855..497fd32 100755
--- a/ci/install-dependencies.sh
+++ b/ci/install-dependencies.sh
@@ -40,11 +40,11 @@ osx-clang|osx-gcc)
test -z "$BREW_INSTALL_PACKAGES" ||
brew install $BREW_INSTALL_PACKAGES
brew link --force gettext
- brew cask install perforce || {
+ brew cask install --no-quarantine perforce || {
# Update the definitions and try again
cask_repo="$(brew --repository)"/Library/Taps/homebrew/homebrew-cask &&
git -C "$cask_repo" pull --no-stat &&
- brew cask install perforce
+ brew cask install --no-quarantine perforce
} ||
brew install caskroom/cask/perforce
case "$jobname" in