.gitlab-ci.yml

###########################################################
# General CI rules:
#           * Create one CI.yml file per language/purpose
#           * Include said CI.yml file below
#           * We use rules in this CI, which means you cannot use only/except
#           * The workflow rules define when the CI gets triggered, job rules are used to define when jobs get triggered
#           * Do not commit any keys/ethereum addresses/private keys/etc directly, use environment variables or other methods
#           * Thank you for reading this far! Get yourself a chocolate as a treat.
###########################################################

variables:
  COMMIT_IMAGE_TAG: $CI_REGISTRY_IMAGE:$CI_COMMIT_REF_NAME
  RELEASE_IMAGE_TAG: $CI_REGISTRY_IMAGE:latest
  PIP_CACHE_DIR: "$CI_PROJECT_DIR/.cache/pip"

# Done to fix this bug: https://gitlab.com/gitlab-org/gitlab/issues/30111#note_275012413
workflow:
  rules:
    - if: $CI_MERGE_REQUEST_IID
      when: never
    - when: always

# defines all the stages in the CI, this includes all stages defined inside the included yml files
stages:
  - build
  - integration
  - bindings
  - wasm
  - rust
  - python
  - dotnet
  - java
  - swift
  - test
  - analysis
  - deploy
  - release

# all the CI files to include and run, they are imported before the CI is started
include:
  - local: "/.gitlab/code-quality.gitlab-ci.yml"
  - local: "/c/ci.yml"
  - local: "/c/ci-analyse.yml"
  - local: "/c/ci-deploy.yml"
  - local: "/wasm/ci.yml"
  - local: "/java/ci.yml"
  - local: "/python/ci.yml"
  - local: "/dotnet/ci.yml"
  - local: "/rust/ci.yml"