add "only" clauses to IDK tests

The IDK tests should be run only when there's changes in the IDK
or client directories.

Also the shard transactional test should be run ever.

The "optional: true" flag is a fascinating quirk allowing you to
express that, *if* a job exists, we should wait for it, but if the
job doesn't exist, that's also acceptable.
This commit is contained in:
Seebs 2022-08-18 14:30:28 -05:00 committed by seebs
parent f066fcb33c
commit 317526cc09

View file

@ -275,6 +275,9 @@ run go tests idk race:
retry: 1
rules:
- if: '$CI_COMMIT_TAG == null && ($CI_PIPELINE_SOURCE == "push" || $CI_PIPELINE_SOURCE == "schedule" || $CI_PIPELINE_SOURCE == "web")'
changes:
- idk
- client
script:
- echo "Running test-all-race"
- cd ./idk/
@ -306,6 +309,9 @@ run go tests idk shard transactional:
retry: 1
rules:
- if: '$CI_COMMIT_TAG == null && ($CI_PIPELINE_SOURCE == "push" || $CI_PIPELINE_SOURCE == "schedule" || $CI_PIPELINE_SOURCE == "web")'
changes:
- idk
- client
script:
- echo "Running shard transactional tests"
- cd ./idk/
@ -346,6 +352,9 @@ run go tests idk 533:
- make shutdown
rules:
- if: '$CI_COMMIT_TAG == null && ($CI_PIPELINE_SOURCE == "push" || $CI_PIPELINE_SOURCE == "schedule" || $CI_PIPELINE_SOURCE == "web")'
changes:
- idk
- client
tags:
- shell
- aws
@ -375,6 +384,9 @@ run go tests idk sasl:
- make shutdown
rules:
- if: '$CI_COMMIT_TAG == null && ($CI_PIPELINE_SOURCE == "push" || $CI_PIPELINE_SOURCE == "schedule" || $CI_PIPELINE_SOURCE == "web")'
changes:
- idk
- client
tags:
- shell
- aws
@ -403,8 +415,13 @@ upload to sonarcloud:
- job: run jest tests
- job: clustertests
- job: run go tests idk race
optional: true
- job: run go tests idk shard transactional
optional: true
- job: run go tests idk sasl
optional: true
- job: run go tests idk 533
optional: true
build for linux arm64:
stage: build
@ -1343,3 +1360,4 @@ cleanup_build_job:
needs:
- job: smoke test
- job: smoke test auth