mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
Don't initialize private testsuite in CI when not running out of Zeek project
The initialization of the private testsuite currently fails builds run in forks. Cirrus's encrypted variables won't work outsize of the Zeek project, so skip that setting altogether.
This commit is contained in:
parent
f269b2ef91
commit
b66e607e5f
1 changed files with 2 additions and 1 deletions
|
@ -31,9 +31,10 @@ fi
|
|||
make update-traces
|
||||
cd ..
|
||||
|
||||
# When running in Cirrus for the main repo, try to clone the private testsuite.
|
||||
# Note that this script is also called when populating the public cache, so
|
||||
# the zeek-testing-private dir could have been created/populated already.
|
||||
if [[ -n "${CIRRUS_CI}" ]] && [[ ! -d zeek-testing-private ]]; then
|
||||
if [[ -n "${CIRRUS_CI}" ]] && [[ "${CIRRUS_REPO_OWNER}" == "zeek" ]] && [[ ! -d zeek-testing-private ]]; then
|
||||
# If we're running this on Cirrus, the SSH key won't be available to PRs,
|
||||
# so don't make any of this fail the task in that case. (But technically,
|
||||
# the key is also available in PRs for people with write access to the
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue