[PATCH v3 3/5] gitlab-ci: Switch to `rules` instead of `except` and `only`

[Uladzimir Bely <ubely@ilbers.de>]

Filters that use `rules` are more configurable and allow using
several rules in the chain.

Also, put `image` under `default` section instead of deprecated
global declaration, with image version update to the latest one.

Signed-off-by: Uladzimir Bely <ubely@ilbers.de>
---
 .gitlab-ci.yml | 15 ++++++++-------
 1 file changed, 8 insertions(+), 7 deletions(-)

diff --git a/.gitlab-ci.yml b/.gitlab-ci.yml
index ded8469b..b700015c 100644
--- a/.gitlab-ci.yml
+++ b/.gitlab-ci.yml
@@ -1,4 +1,5 @@
-image: ghcr.io/siemens/kas/kas-isar:3.2.3
+default:
+  image: ghcr.io/siemens/kas/kas-isar:3.2.3
 
 variables:
   GIT_STRATEGY: clone
@@ -24,22 +25,22 @@ variables:
 
 dev-ci:
   <<: *common-build
-  except:
-    - schedules
+  rules:
+    - if: $CI_PIPELINE_SOURCE != 'schedule'
   script:
     - scripts/ci_build.sh -T dev
 
 fast-ci:
   <<: *common-build
-  only:
-    - schedules
+  rules:
+    - if: $CI_PIPELINE_SOURCE == 'schedule'
   script:
     - scripts/ci_build.sh -T fast
 
 full-ci:
   <<: *common-build
-  only:
-    - schedules
+  rules:
+    - if: $CI_PIPELINE_SOURCE == 'schedule'
   script:
     - PREVIOUS_SHA="$(cat .CI_COMMIT_SHA || true)"
     - if [ "$CI_COMMIT_SHA" != "$PREVIOUS_SHA" ]; then
-- 
2.20.1