# This sets when pipelines are created. Jobs have more specific rules to restrict them.
@@ -13,7 +20,6 @@ workflow:
-if:$CI_PIPELINE_SOURCE == 'push' && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH# Pushes to main
-if:$CI_PIPELINE_SOURCE == 'schedule' && $CI_COMMIT_BRANCH == $CI_DEFAULT_BRANCH# Scheduled in main
stages:
-maintenance
-build
@@ -51,6 +57,8 @@ stages:
rules:
-if:$MIRROR_ACCESS_TOKEN# Don't run in the mirror update pipeline (only then MIRROR_ACCESS_TOKEN is defined)
when:never
-if:$CI_PIPELINE_SOURCE == 'schedule'# Don't run in any scheduled pipelines by default (use schedule templates below to enable again for certain conditions)
when:never
-when:on_success
.rules-merge-request:
@@ -216,6 +224,12 @@ msan-on-merge-request-linux:
-python3 scripts/self_test.py --create | tee test_output.txt
-if [ $exit_code -eq 1 ] && [ $zero_errors == 1 ]; then echo "pytest run had failures, but no errors and non-BE flag present"; exit $EXIT_CODE_NON_BE; fi
-if [ $exit_code -ne 0 ]; then echo "pytest run had errors"; exit $EXIT_CODE_FAIL; fi;
# return exit code from selftest if everything went well with the pytest run
-if [ $exit_code -eq 1 ] && [ $zero_errors == 1 ]; then echo "pytest run had failures, but no errors and non-BE flag present"; exit $EXIT_CODE_NON_BE; fi
-if [ $exit_code -ne 0 ]; then echo "pytest run had errors"; exit $EXIT_CODE_FAIL; fi;
# return exit code from selftest if everything went well with the pytest run