JUnit i GitLab CI me Kubernetes

Ahakoa te mea e tino mohio ana te katoa he mea nui, he mea tika hoki te whakamatautau i to rorohiko, a he maha nga mea kua mahi aunoa mo te wa roa, i roto i te whanuitanga o Habr karekau he tohutaka kotahi mo te whakatuu huinga o aua hua rongonui i roto tenei kohanga hei (ta maatau tino pai) GitLab me JUnit . Kia whakakiia tenei waahi!

JUnit i GitLab CI me Kubernetes

Whakataki

Tuatahi, me hoatu e ahau etahi horopaki:

  • I te mea ko o maatau tono katoa kei runga i nga Kubernetes, ka whakaarohia e maatau nga whakamatautau mo nga hanganga tika.
  • Mo te huihuinga me te tohatoha ka whakamahia e matou werf (i runga i nga waahanga hangahanga, ko te tikanga ano kei te uru a Helm).
  • E kore ahau e haere ki nga korero mo te hanga o nga whakamatautau: i roto i ta maatau keehi, ka tuhia e te kaihoko nga whakamatautau ia ia ano, a ka whakarite noa matou i to raatau whakarewatanga (me te aroaro o te ripoata e pa ana ki te tono hanumi).


He aha te ahua o te raupapa mahi?

  1. Te hanga i te tono - ka waiho e matou te whakaahuatanga o tenei waahanga.
  2. Tukuna te tono ki tetahi mokowāingoa motuhake o te kāhui Kubernetes ka timata ki te whakamatautau.
  3. Te rapu mo nga taonga toi me te tarai i nga purongo JUnit me GitLab.
  4. Te muku i te mokowāingoa i hangaia i mua.

Inaianei - ki te whakatinanatanga!

whakatikatikanga

GitLab CI

Me timata ma te wahanga .gitlab-ci.yaml, e whakaahua ana i te tohatoha i te tono me te whakahaere i nga whakamatautau. Ko te rarangi i puta he tino puhoi, no reira i tino taapirihia ki nga korero:

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

Inaianei kei te raarangi .helm/templates me hanga YAML me Job - tests-job.yaml — ki te whakahaere i nga whakamatautau me nga rauemi Kubernetes e hiahiatia ana. Tirohia nga whakamaramatanga i muri i te raarangi:

{{- 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 }}

He aha te momo rauemi whakaahuatia i roto i tenei whirihoranga? I te wa e tohatoha ana, ka hangaia e matou he mokowā ingoa ahurei mo te kaupapa (kua tohuhia tenei ki roto .gitlab-ci.yaml - tests-${CI_COMMIT_REF_SLUG}) ka hurihia ki waho:

  1. Mahere Whirihora me te tuhinga whakamatautau;
  2. Job me te whakamaarama o te peera me te tohutohu kua tohua command, ka whakahaere noa i nga whakamatautau;
  3. PV me te PVC, ka taea e koe te rokiroki raraunga whakamatautau.

Kia whai whakaaro ki te huru whakataki ki if i te timatanga o te whakaaturanga - na reira, me takai etahi atu konae YAML o te tūtohi Helm me te tono. whakamuri hoahoa kia kore e tukuna i te wa o te whakamatautau. Koina:

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

Heoi, mena ko nga whakamatautau me hiahia etahi hanganga (hei tauira, Redis, RabbitMQ, Mongo, PostgreSQL...) - ka taea o raatau YAML e kore whakaweto. Hoatuhia ki roto i te taiao whakamatautau ... whakatikahia kia rite ki taau e pai ai, o te akoranga.

Tapa whakamutunga

No te mea te huihuinga me te tohatoha ma te whakamahi i nga mahi werf mo tenei wa anake i runga i te tūmau hanga (me te gitlab-runner), ka whakarewahia te pod me nga whakamatautau ki runga i te rangatira, me hanga e koe he whaiaronga. /mnt/tests i runga i te rangatira ka hoatu ki te kai oma; hei tauira, mā NFS. He tauira taipitopito me nga whakamarama ka kitea i roto K8s tuhinga.

Ko te hua ka:

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

Karekau he tangata e aukati i te hanga tiritiri NFS tika ki runga i te gitlab-runner, katahi ka whakairihia ki roto i nga poro.

parau

Kei te patai pea koe he aha i whakararu ai i nga mea katoa ma te hanga Hopa mena ka taea e koe te whakahaere i tetahi tuhinga me nga whakamatautau tika ki runga i te kaikawe anga? He iti noa te whakautu...

Ko etahi o nga whakamatautau me uru ki te hanganga (MongoDB, RabbitMQ, PostgreSQL, me etahi atu) hei manatoko kei te mahi tika. Ka whakakotahihia e matou nga whakamatautau - na tenei huarahi, ka ngawari ki te whakauru i etahi atu hinonga. I tua atu i tenei, ka whiwhi tatou paerewa huarahi tohatoha (ahakoa te whakamahi i te NFS, te taapiri atu o nga raarangi whaiaronga).

hua

He aha ta tatou e kite ina tono tatou i te whirihoranga kua whakaritea?

Ka whakaatuhia e te tono hanumi nga tatauranga whakarāpopototanga mo nga whakamatautau e whakahaerehia ana i roto i tana paipa hou:

JUnit i GitLab CI me Kubernetes

Ka taea te paato i ia hapa ki konei mo nga taipitopito:

JUnit i GitLab CI me Kubernetes

NB: Ka kite te kaipanui whakarongo kei te whakamatautauhia e matou he tono NodeJS, a, i roto i nga whakaahua - .NET... Kaua e miharo: ko te mea i te wa e whakarite ana i te tuhinga, kaore he hapa i kitea i te whakamatautau i te tono tuatahi, engari ko ratou. i kitea i tetahi atu.

mutunga

Ka kite koe, kaore he mea uaua!

Ko te tikanga, mena kei a koe he kaikohi anga kua mahi, engari kaore koe e hiahia ki nga Kubernetes, ko te taapiri whakamatautau ki a ia he mahi ngawari ake i te korero i konei. Na roto GitLab CI tuhinga ka kitea e koe etahi tauira mo Ruby, Haere, Gradle, Maven me etahi atu.

PS

Pānuihia hoki i runga i ta maatau blog:

Source: will.com

Tāpiri i te kōrero