Table of Contents
Files that allows to run Apache Airflow system tests. They are executed in Google Cloud Build by Airflow Breeze.
Instruction how create Google Cloud Project for system tests is available in airflow-providers-google-setup
folder.
See instructions: airflow-providers-google-setup/README.md
Modify following files:
system_tests/cloudbuild.yaml
- so_SERVICE_ACCOUNTS_GCS_BUCKET
will point to bucket with service accounts. It is created in the previous step (output ofterraform apply
command prints bucket nameservice_account_bucket_name
).system_tests/cloudbuild.yaml
- soLOGS_GCS_BUCKET
will point to bucket where Cloud Build logs will be uploaded. It is created in the previous step (output ofterraform apply
command prints bucket namecloud_build_logs_bucket_name
).scripts/list_of_tests.sh
- comment / uncomment out tests which are / are not intended to run.
In airflow_system_tests_env_image
folder is located Dockerfile
which describes environment to run Breeze
(see Breeze prerequisites).
To build image and push it to GCR:
cd airflow_system_tests_env_image
gcloud builds submit .
Docker image will be available at gcr.io/$PROJECT_ID/airflow-system-tests-env:latest
.
They will be executed by default on apache/airflow
repository on master
branch
gcloud builds submit --config=cloudbuild_system_tests.yaml
Command to list all triggered builds will be in the last line of the log, e.g.:
List runs with command:
gcloud builds list --filter "tags='trigger-fdb3a03b-1f99-45fa-8dcb-5cf4d6ca3828'" --format="table[box,margin=3,title='system tests'](id,status,tags,logUrl)"
It will be executed by default on apache/airflow
repository on master
branch.
bash scripts/run_single_system_test.sh tests/providers/google/cloud/operators/test_speech_to_text_system.py
Example of the command to run Google Memorystore system tests on the Airflow fork and non-default branch.
CMD="./breeze tests --verbose --backend=postgres tests/providers/google/cloud/operators/test_cloud_memorystore_system.py -- -s --system=google"
AIRFLOW_REPO="https://github.com/PolideaInternal/airflow"
BRANCH="fix-to-issue-8286-cloud-memorystore-memcached-operators"
cd system_tests
gcloud builds submit \
--timeout=3600 \
--substitutions _CMD="${CMD}",_AIRFLOW_REPO="${AIRFLOW_REPO}",_BRANCH="${BRANCH}"
Setting --timeout
for system tests is recommended.
Configuration is located in system_tests
folder. It supports following substitutions:
Substitution | Default value | Description |
---|---|---|
_CMD |
./breeze tests --verbose --backend=postgres tests/providers/google/cloud/operators/test_natural_language_system.py -- -s --system=google |
Bash command run in airflow-system-tests-env . See Docker image to run Breeze |
_AIRFLOW_REPO |
https://github.com/apache/airflow |
URL of the Airflow git repository. |
_BRANCH |
master |
Name of the branch to checkout. |
_TAG_TRIGGER_TYPE |
trigger-manual |
Tag added do GCB build |
_TAG_TEST_NAME |
test-name-not-specified |
Tag added do GCB build |
_LOGS_GCS_BUCKET |
airflow-system-tests-logs |
GCS bucket where tests logs are uploaded |
_SERVICE_ACCOUNTS_GCS_BUCKET |
airflow-systest-project-system-tests-rlugtuhw |
GCS bucket where service accounts keys are stored (it is output from airflow-providers-google-setup/terraform/modules/service_accounts_setup/outputs.tf , see: airflow-providers-google-setup/README.md) |