Skip to content

Commit 6196610

Browse files
dschoGit for Windows Build Agent
authored and
Git for Windows Build Agent
committed
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 <[email protected]>
1 parent 2c037b4 commit 6196610

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

ci/install-dependencies.sh

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,11 +40,11 @@ osx-clang|osx-gcc)
4040
test -z "$BREW_INSTALL_PACKAGES" ||
4141
brew install $BREW_INSTALL_PACKAGES
4242
brew link --force gettext
43-
brew cask install perforce || {
43+
brew cask install --no-quarantine perforce || {
4444
# Update the definitions and try again
4545
cask_repo="$(brew --repository)"/Library/Taps/homebrew/homebrew-cask &&
4646
git -C "$cask_repo" pull --no-stat &&
47-
brew cask install perforce
47+
brew cask install --no-quarantine perforce
4848
} ||
4949
brew install caskroom/cask/perforce
5050
case "$jobname" in

0 commit comments

Comments
 (0)