| commit | 5ed9fc3fc8629d9c13b6bae03a32e28cf8be3e96 | |
| author | Johannes Schindelin <johannes.schindelin@gmx.de> | |
| Thu, 27 Feb 2020 13:23:12 +0000 (27 13:23 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Thu, 27 Feb 2020 17:58:42 +0000 (27 09:58 -0800) | ||
| tree | 946a8cab8099a916f1b9f495044b3e8fc19c3263 | treesnapshot (tar.gz zip) |
| parent | eafff6e41e6a16c23764dcd31373bedd61572cf1 | commitdiff |
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>
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>
| ci/install-dependencies.sh | diffblobblamehistory |