🥇JUnit na GitLab CI ya na Kubernetes

N'agbanyeghị na onye ọ bụla maara nke ọma na ịnwale ngwanrọ gị dị mkpa ma dị mkpa, na ọtụtụ ndị na-eme ya na-akpaghị aka ruo ogologo oge, na nnukwu Habr ọ dịghị otu ntụziaka maka ịmepụta ngwakọta nke ngwaahịa ndị a ma ama na. niche a dị ka (ọkacha mmasị anyị) GitLab na JUnit. Ka anyị mejupụta oghere a!

Okwu mmalite

Nke mbụ, ka m nye nkọwa ụfọdụ:

Ebe ọ bụ na ngwa anyị niile na-agba na Kubernetes, anyị ga-atụle ịnwale ule na akụrụngwa kwesịrị ekwesị.
Maka mgbakọ na ntinye anyị na-eji werf (n'ihe gbasara akụrụngwa akụrụngwa, nke a pụtakwara ozugbo na Helm na-etinye aka).
M ga-aga n'ime nkọwa nke n'ezie e kere eke nke ule: na anyị ikpe, ndị ahịa na-ede ule onwe ya, na anyị naanị hụ na ha igba egbe (na ọnụnọ nke a kwekọrọ ekwekọ akụkọ na jikota arịrịọ).

Kedu ka usoro omume izugbe ga-adị ka?

Iwuli ngwa ngwa - anyị ga-ahapụ nkọwa nke ọkwa a.
Nyefee ngwa ahụ na oghere aha dị iche nke ụyọkọ Kubernetes wee malite ịnwale.
Ịchọ artifact na iji GitLab na-enyocha akụkọ JUnit.
Na-ehichapụ oghere aha emepụtara mbụ.

Ugbu a - ka mmejuputa iwu!

ukpụhọde

GitLab CI

Ka anyị malite na iberibe .gitlab-ci.yaml, nke na-akọwa itinye ngwa na ule na-agba ọsọ. Ndepụta ahụ tụgharịrị bụrụ nke ukwuu, ya mere ejiri nkọwa gbakwunye ya nke ọma:

variables:
# объявляем версию werf, которую собираемся использовать
  WERF_VERSION: "1.0 beta"

.base_deploy: &base_deploy
  script:
# создаем namespace в K8s, если его нет
    - kubectl --context="${WERF_KUBE_CONTEXT}" get ns ${CI_ENVIRONMENT_SLUG} || kubectl create ns ${CI_ENVIRONMENT_SLUG}
# загружаем werf и деплоим — подробнее об этом см. в документации
# (https://werf.io/how_to/gitlab_ci_cd_integration.html#deploy-stage)
    - type multiwerf && source <(multiwerf use ${WERF_VERSION})
    - werf version
    - type werf && source <(werf ci-env gitlab --tagging-strategy tag-or-branch --verbose)
    - werf deploy --stages-storage :local
      --namespace ${CI_ENVIRONMENT_SLUG}
      --set "global.commit_ref_slug=${CI_COMMIT_REF_SLUG:-''}"
# передаем переменную `run_tests`
# она будет использоваться в рендере Helm-релиза
      --set "global.run_tests=${RUN_TESTS:-no}"
      --set "global.env=${CI_ENVIRONMENT_SLUG}"
# изменяем timeout (бывают долгие тесты) и передаем его в релиз
      --set "global.ci_timeout=${CI_TIMEOUT:-900}"
     --timeout ${CI_TIMEOUT:-900}
  dependencies:
    - Build

.test-base: &test-base
  extends: .base_deploy
  before_script:
# создаем директорию для будущего отчета, исходя из $CI_COMMIT_REF_SLUG
    - mkdir /mnt/tests/${CI_COMMIT_REF_SLUG} || true
# вынужденный костыль, т.к. GitLab хочет получить артефакты в своем build-dir’е
    - mkdir ./tests || true
    - ln -s /mnt/tests/${CI_COMMIT_REF_SLUG} ./tests/${CI_COMMIT_REF_SLUG}
  after_script:
# после окончания тестов удаляем релиз вместе с Job’ом
# (и, возможно, его инфраструктурой)
    - type multiwerf && source <(multiwerf use ${WERF_VERSION})
    - werf version
    - type werf && source <(werf ci-env gitlab --tagging-strategy tag-or-branch --verbose)
    - werf dismiss --namespace ${CI_ENVIRONMENT_SLUG} --with-namespace
# мы разрешаем падения, но вы можете сделать иначе
  allow_failure: true
  variables:
    RUN_TESTS: 'yes'
# задаем контекст в werf
# (https://werf.io/how_to/gitlab_ci_cd_integration.html#infrastructure)
    WERF_KUBE_CONTEXT: 'admin@stage-cluster'
  tags:
# используем раннер с тегом `werf-runner`
    - werf-runner
  artifacts:
# требуется собрать артефакт для того, чтобы его можно было увидеть
# в пайплайне и скачать — например, для более вдумчивого изучения
    paths:
      - ./tests/${CI_COMMIT_REF_SLUG}/*
# артефакты старше недели будут удалены
    expire_in: 7 day
# важно: эти строки отвечают за парсинг отчета GitLab’ом
    reports:
      junit: ./tests/${CI_COMMIT_REF_SLUG}/report.xml

# для упрощения здесь показаны всего две стадии
# в реальности же у вас их будет больше — как минимум из-за деплоя
stages:
  - build
  - tests

build:
  stage: build
  script:
# сборка — снова по документации по werf
# (https://werf.io/how_to/gitlab_ci_cd_integration.html#build-stage)
    - type multiwerf && source <(multiwerf use ${WERF_VERSION})
    - werf version
    - type werf && source <(werf ci-env gitlab --tagging-strategy tag-or-branch --verbose)
    - werf build-and-publish --stages-storage :local
  tags:
    - werf-runner
  except:
    - schedules

run tests:
  <<: *test-base
  environment:
# "сама соль" именования namespace’а
# (https://docs.gitlab.com/ce/ci/variables/predefined_variables.html)
    name: tests-${CI_COMMIT_REF_SLUG}
  stage: tests
  except:
    - schedules

Kubernetes

Ugbu a na ndekọ .helm/templates ka anyị jiri Job mepụta YAML - tests-job.yaml - iji mee ule na akụrụngwa Kubernetes ọ chọrọ. Hụ nkọwa mgbe ịdepụtachara:

{{- if eq .Values.global.run_tests "yes" }}
---
apiVersion: v1
kind: ConfigMap
metadata:
  name: tests-script
data:
  tests.sh: |
    echo "======================"
    echo "${APP_NAME} TESTS"
    echo "======================"

    cd /app
    npm run test:ci
    cp report.xml /app/test_results/${CI_COMMIT_REF_SLUG}/

    echo ""
    echo ""
    echo ""

    chown -R 999:999 /app/test_results/${CI_COMMIT_REF_SLUG}
---
apiVersion: batch/v1
kind: Job
metadata:
  name: {{ .Chart.Name }}-test
  annotations:
    "helm.sh/hook": post-install,post-upgrade
    "helm.sh/hook-weight": "2"
    "werf/watch-logs": "true"
spec:
  activeDeadlineSeconds: {{ .Values.global.ci_timeout }}
  backoffLimit: 1
  template:
    metadata:
      name: {{ .Chart.Name }}-test
    spec:
      containers:
      - name: test
        command: ['bash', '-c', '/app/tests.sh']
{{ tuple "application" . | include "werf_container_image" | indent 8 }}
        env:
        - name: env
          value: {{ .Values.global.env }}
        - name: CI_COMMIT_REF_SLUG
          value: {{ .Values.global.commit_ref_slug }}
       - name: APP_NAME
          value: {{ .Chart.Name }}
{{ tuple "application" . | include "werf_container_env" | indent 8 }}
        volumeMounts:
        - mountPath: /app/test_results/
          name: data
        - mountPath: /app/tests.sh
          name: tests-script
          subPath: tests.sh
      tolerations:
      - key: dedicated
        operator: Exists
      - key: node-role.kubernetes.io/master
        operator: Exists
      restartPolicy: OnFailure
      volumes:
      - name: data
        persistentVolumeClaim:
          claimName: {{ .Chart.Name }}-pvc
      - name: tests-script
        configMap:
          name: tests-script
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: {{ .Chart.Name }}-pvc
spec:
  accessModes:
  - ReadWriteOnce
  resources:
    requests:
      storage: 10Mi
  storageClassName: {{ .Chart.Name }}-{{ .Values.global.commit_ref_slug }}
  volumeName: {{ .Values.global.commit_ref_slug }}

---
apiVersion: v1
kind: PersistentVolume
metadata:
  name: {{ .Values.global.commit_ref_slug }}
spec:
  accessModes:
  - ReadWriteOnce
  capacity:
    storage: 10Mi
  local:
    path: /mnt/tests/
  nodeAffinity:
   required:
     nodeSelectorTerms:
     - matchExpressions:
       - key: kubernetes.io/hostname
         operator: In
         values:
         - kube-master
  persistentVolumeReclaimPolicy: Delete
  storageClassName: {{ .Chart.Name }}-{{ .Values.global.commit_ref_slug }}
{{- end }}

Kedu ụdị akụrụngwa kọwara na nhazi a? Mgbe a na-ebuga ya, anyị na-emepụta oghere aha pụrụ iche maka ọrụ ahụ (nke a gosipụtara na .gitlab-ci.yaml - tests-${CI_COMMIT_REF_SLUG}) ma tụgharịa ya:

ConfigMap ya na edemede ule;
Job na nkọwa nke pọd na ntuziaka akọwapụtara command, nke na-agba ọsọ ule;
PV na PVC, nke na-enye gị ohere ịchekwa data ule.

Lezienụ anya na ọnọdụ mmeghe na if na mmalite nke ngosipụta - ya mere, faịlụ YAML ndị ọzọ nke eserese Helm nwere ngwa a ga-etinyerịrị na ya laa azu imewe ka ha ghara ibuga n'oge ule. Ya bụ:

{{- if ne .Values.global.run_tests "yes" }}
---
я другой ямлик
{{- end }}

Otú ọ dị, ọ bụrụ na ule chọrọ ụfọdụ akụrụngwa (dịka ọmụmaatụ, Redis, RabbitMQ, Mongo, PostgreSQL...) - YAML ha nwere ike ịbụ bụghị gbanyụọ. Tinye ha n'ime ebe ule dị ka nke ọma ... na-edozi ha dị ka ịchọrọ, n'ezie.

mmetụ ikpeazụ

N'ihi na mgbakọ na ntinye aka site na iji werf na-arụ ọrụ ugbu a naanị na ihe nkesa na-ewu ụlọ (ya na gitlab-runner), na pod nwere ule na-amalite na nna ukwu, ị ga-achọ ịmepụta ndekọ. /mnt/tests na nna ukwu ma nye ya onye na-agba ọsọ, dịka ọmụmaatụ, site na NFS. Enwere ike ịchọta ihe atụ zuru ezu na nkọwa Akwụkwọ K8s.

Nsonaazụ ga-abụ:

user@kube-master:~$ cat /etc/exports | grep tests
/mnt/tests    IP_gitlab-builder/32(rw,nohide,insecure,no_subtree_check,sync,all_squash,anonuid=999,anongid=998)

user@gitlab-runner:~$ cat /etc/fstab | grep tests
IP_kube-master:/mnt/tests    /mnt/tests   nfs4    _netdev,auto  0       0

Ọ dịghị onye machibidoro ime NFS òkè ozugbo na gitlab-ọsọ, wee na-ebuli ya na pọd.

Примечание

Ị nwere ike na-ajụ ihe mere na-agbagwoju ihe niile site na-eke a Job ma ọ bụrụ na ị nwere ike na-agba ọsọ a script na ule ozugbo na shei na-agba ọsọ? Azịza ya dị nnọọ obere ...

Ụfọdụ ule chọrọ ịnweta akụrụngwa (MongoDB, RabbitMQ, PostgreSQL, wdg) iji chọpụta na ha na-arụ ọrụ nke ọma. Anyị na-eme ka nnwale dị n'otu - site na usoro a, ọ ga-adị mfe itinye ihe ndị ọzọ. Na mgbakwunye na nke a, anyị na-enweta ọkọlọtọ nsonye ntinye (ọbụlagodi ma ọ bụrụ na iji NFS, ntinye akwụkwọ ndekọ aha ọzọ).

N'ihi

Kedu ihe anyị ga-ahụ mgbe anyị na-etinye nhazi a kwadebere?

Arịrịọ nchikota ga-egosi nchịkọta nchịkọta maka ule emere na pipeline ya kacha ọhụrụ:

Enwere ike ịpị mperi ọ bụla ebe a maka nkọwa:

NB: Onye na-agụ na-ege ntị ga-achọpụta na anyị na-anwale ngwa NodeJS, na na nseta ihuenyo - .NET ... Atụla gị anya: ọ bụ naanị na mgbe ị na-akwadebe isiokwu ahụ, ọ dịghị njehie ahụghị na ịnwale ngwa mbụ, ma ha a chọtara na nke ọzọ.

nkwubi

Dị ka ị pụrụ ịhụ, ọ dịghị ihe mgbagwoju anya!

Na ụkpụrụ, ọ bụrụ na ịnweelarị onye na-anakọta shei ma ọ na-arụ ọrụ, mana ị chọghị Kubernetes, itinye ule na ya ga-abụ ọrụ dị mfe karịa ka akọwara ebe a. Na n'ime Akwụkwọ GitLab CI Ị ga-ahụ ihe atụ maka Ruby, Go, Gradle, Maven na ụfọdụ ndị ọzọ.

PS

Gụọkwa na blọọgụ anyị:

isi: www.habr.com

JUnit na GitLab CI ya na Kubernetes