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>
Johannes Schindelin committed
Feb 27, 2020 at 13:23 UTC
5ed9fc3fc8629d9c13b6bae03a32e28cf8be3e96
1 file changed
+2
-2
ci/install-dependencies.sh
+2
-2
@@ -40,11 +40,11 @@ osx-clang|osx-gcc)
40
test -z "$BREW_INSTALL_PACKAGES" ||
41
brew install $BREW_INSTALL_PACKAGES
42
brew link --force gettext
43
- brew cask install perforce || {
43
+ brew cask install --no-quarantine perforce || {
44
# Update the definitions and try again
45
cask_repo="$(brew --repository)"/Library/Taps/homebrew/homebrew-cask &&
46
git -C "$cask_repo" pull --no-stat &&
47
- brew cask install perforce
47
+ brew cask install --no-quarantine perforce
48
} ||
49
brew install caskroom/cask/perforce
50
case "$jobname" in