Lesi sihloko sizoba nentshisekelo kubo bobabili abahloli nabathuthukisi, kodwa sihloselwe ikakhulukazi ochwepheshe bokuzenzakalela ababhekene nenkinga yokusetha i-GitLab CI/CD yokuhlolwa kokuhlanganiswa ngaphansi kwezimo zokunganele kwezinsiza zengqalasizinda kanye/noma ukungabikho kwesiqukathi. inkundla ye-orchestration. Ngizokutshela ukuthi ungamisa kanjani ukuthunyelwa kwezindawo zokuhlola usebenzisa i-docker compose kumgijimi wegobolondo elilodwa le-GitLab futhi ukuze lapho kuthunyelwa izindawo ezimbalwa, izinsiza eziqalisiwe zingaphambanisani.
Okuqukethwe
Okudingekayo
-
Emsebenzini wami, kwakuvamile ukuthi ukuhlolwa kokuhlanganiswa "kwelashwe" kumaphrojekthi. Futhi ngokuvamile inkinga yokuqala nebaluleke kakhulu ipayipi le-CI, lapho ukuhlolwa kokuhlanganiswa iyathuthukiswa amasevisi enziwa endaweni ye-dev/stage. Lokhu kubangele izinkinga ezimbalwa:
- Ngenxa yokukhubazeka kusevisi ethile ngesikhathi sokuhlolwa kokuhlanganiswa, isifunda sokuhlola singalimala idatha ephukile. Kube nezimo lapho ukuthunyelwa kwesicelo ngefomethi ye-JSON ephukile kuphahlazeka isevisi, okunikeze isitendi singasebenzi ngokuphelele.
- Ukwehla kwesekethe yokuhlola njengoba idatha yokuhlola ikhula. Ngicabanga ukuthi akunangqondo ukuchaza isibonelo ngokuhlanza/ukubuyisela emuva isizindalwazi. Emsebenzini wami, angizange ngihlangabezane nephrojekthi lapho le nqubo ihambe kahle.
- Ingozi yokuphazamisa ukusebenza kwesekethe yokuhlola lapho kuhlolwa izilungiselelo zesistimu evamile. Isibonelo, inqubomgomo yomsebenzisi/iqembu/iphasiwedi/yohlelo lokusebenza.
- Idatha yokuhlola evela ezivivinyweni ezizenzakalelayo yenza impilo ibe nzima kubahloli abazenzelayo.
Abanye bazothi ama-autotes amahle kufanele ahlanze idatha ngemuva kwawo. Nginokuphikisa:
- Izitendi ezinamandla kulula kakhulu ukuzisebenzisa.
- Akuzona zonke izinto ezingasuswa ohlelweni nge-API. Isibonelo, ikholi yokususa into ayizange isetshenziswe ngoba iphikisana nokucabanga kwebhizinisi.
- Lapho udala into nge-API, inani elikhulu lemethadatha lingadalwa, okuyinkinga ukulisusa.
- Uma izivivinyo zinokuncika phakathi kwazo, khona-ke inqubo yokuhlanza idatha ngemuva kokuhlola iphenduka ibe yikhanda elibuhlungu.
- Izingcingo ezengeziwe (futhi, ngokubona kwami, azilungisisiwe) eziya ku-API.
- Futhi impikiswano eyinhloko: lapho idatha yokuhlola iqala ukusulwa ngokuqondile kusizindalwazi. Lokhu kuphenduka isekisi langempela le-PK/FK! Sizwa ngonjiniyela: "Ngisanda kwengeza/ngikhiphe/ngiqambe kabusha uphawu, kungani kubanjwe izivivinyo zokuhlanganisa eziyi-100500?"
Ngokubona kwami, ikhambi elifaneleka kakhulu yindawo eguquguqukayo.
- Abantu abaningi basebenzisa i-docker-compose ukuze baqhube indawo yokuhlola, kodwa bambalwa abantu abasebenzisa i-docker-compose lapho benza ukuhlola kokuhlanganisa ku-CI/CD. Futhi lapha anginaki i-kubernetes, uswarm nezinye izinkundla ze-orchestration. Akuzona zonke izinkampani ezinazo. Kungaba kuhle uma i-docker-compose.yml ibikhona yonke indawo.
- Noma sinomgijimi we-QA wethu, singenza kanjani isiqiniseko sokuthi izinsiza eziqaliswe nge-docker-compose aziphazamisi zodwa?
- Ungawaqoqa kanjani amalogi ezinsiza ezihloliwe?
- Indlela yokuhlanza umgijimi?
Nginomgijimi wami we-GitLab wamaphrojekthi ami futhi ngihlangabezane nale mibuzo ngesikhathi sokuthuthukiswa ngoba . Ngokunembayo, lapho wenza izivivinyo zokuhlanganisa. Ngezansi sizoxazulula lezi zinkinga sisebenzisa izibonelo zale phrojekthi.
I-GitLab Shell Runner
Kumgijimi, ngincoma umshini obonakalayo we-Linux one-4 vCPU, 4 GB RAM, 50 GB HDD.
Kunolwazi oluningi ngokusetha i-gitlab-runner ku-inthanethi, ngamafuphi:
- Ngena ngemvume emshinini nge-SSH
-
Uma une-RAM engaphansi kuka-8 GB, ngincoma ukuze umbulali we-OOM angezi azobulala imisebenzi yethu ngenxa yokuntuleka kwe-RAM. Lokhu kungenzeka uma imisebenzi engaphezu kwemi-5 yethulwa kanyekanye. Imisebenzi izothuthuka kancane, kodwa kancane kancane.
Isibonelo nge-OOM killer
Uma ubona kulogi lomsebenzi
bash: line 82: 26474 Killed, bese uvele ukhiphe kumgijimisudo dmesg | grep 26474[26474] 1002 26474 1061935 123806 339 0 0 java Out of memory: Kill process 26474 (java) score 127 or sacrifice child Killed process 26474 (java) total-vm:4247740kB, anon-rss:495224kB, file-rss:0kB, shmem-rss:0kBFuthi uma isithombe sibukeka kanje, bese ungeza ukushintshanisa noma wengeze i-RAM.
- Faka , , , yenza.
- Ukwengeza umsebenzisi
gitlab-runnereqenjinidockersudo groupadd docker sudo usermod -aG docker gitlab-runner - gitlab-runner.
-
Vula ukuze uhlelwe
/etc/gitlab-runner/config.tomlbese wengezaconcurrent=20 [[runners]] request_concurrency = 10Lokhu kuzokuvumela ukuthi wenze imisebenzi ehambisanayo kumgijimi oyedwa. Funda kabanzi .
Uma unomshini onamandla kakhulu, isibonelo i-8 vCPU, i-RAM engu-16 GB, khona-ke lezi zinombolo zingenziwa okungenani izikhathi ezi-2 ezinkulu. Kodwa konke kuncike ekutheni yini ngempela ezokwethulwa kulo mgijimi nokuthi ngenani elingakanani.
Sekwanele.
Ilungiselela i-docker-compose.yml
Umsebenzi oyinhloko yi-universal docker-compose.yml, onjiniyela/abahloli abangayisebenzisa kokubili endaweni kanye nepayipi le-CI.
Okokuqala, senza amagama esevisi ahlukile e-CI. Okunye okuhlukile okuhlukile ku-GitLab CI ukuguquguquka CI_JOB_ID. Uma ucacise container_name ngencazelo "service-${CI_JOB_ID:-local}", bese esimweni:
- uma
CI_JOB_IDakuchazwa eziguquguqukayo zemvelo,
khona-ke igama lenkonzo lizobaservice-local - uma
CI_JOB_IDkuchazwa eziguquguqukayo zemvelo (isibonelo 123),
khona-ke igama lenkonzo lizobaservice-123
Okwesibili, sakha inethiwekhi evamile yezinsizakalo eziqalisiwe. Lokhu kusinika ukuhlukaniswa kweleveli yenethiwekhi lapho sisebenzisa izindawo eziningi zokuhlola.
networks:
default:
external:
name: service-network-${CI_JOB_ID:-local}Empeleni, lesi isinyathelo sokuqala sempumelelo =)
Isibonelo se-docker-compose.yml yami enamazwana
version: "3"
# Для корректной работы web (php) и fmt нужно,
# чтобы контейнеры имели общий исполняемый контент.
# В нашем случае, это директория /var/www/testrail
volumes:
static-content:
# Изолируем окружение на сетевом уровне
networks:
default:
external:
name: testrail-network-${CI_JOB_ID:-local}
services:
db:
image: mysql:5.7.22
# Каждый container_name содержит ${CI_JOB_ID:-local}
container_name: "testrail-mysql-${CI_JOB_ID:-local}"
environment:
MYSQL_HOST: db
MYSQL_DATABASE: mydb
MYSQL_ROOT_PASSWORD: 1234
SKIP_GRANT_TABLES: 1
SKIP_NETWORKING: 1
SERVICE_TAGS: dev
SERVICE_NAME: mysql
networks:
- default
migration:
image: registry.gitlab.com/touchbit/image/testrail/migration:latest
container_name: "testrail-migration-${CI_JOB_ID:-local}"
links:
- db
depends_on:
- db
networks:
- default
fpm:
image: registry.gitlab.com/touchbit/image/testrail/fpm:latest
container_name: "testrail-fpm-${CI_JOB_ID:-local}"
volumes:
- static-content:/var/www/testrail
links:
- db
networks:
- default
web:
image: registry.gitlab.com/touchbit/image/testrail/web:latest
container_name: "testrail-web-${CI_JOB_ID:-local}"
# Если переменные TR_HTTP_PORT или TR_HTTPS_PORTS не определены,
# то сервис поднимается на 80 и 443 порту соответственно.
ports:
- ${TR_HTTP_PORT:-80}:80
- ${TR_HTTPS_PORT:-443}:443
volumes:
- static-content:/var/www/testrail
links:
- db
- fpm
networks:
- defaultIsibonelo sokugijima kwendawo
docker-compose -f docker-compose.yml up -d
Starting testrail-mysql-local ... done
Starting testrail-migration-local ... done
Starting testrail-fpm-local ... done
Recreating testrail-web-local ... doneKepha akuyona yonke into elula kakhulu ngokwethula ku-CI.
Ilungiselela i-Makefile
Ngisebenzisa i-Makefile ngoba ilungele kakhulu kokubili ukuphathwa kwemvelo yendawo kanye naku-CI. Amazwana amaningi aku-inthanethi
# У меня в проектах все вспомогательные вещи лежат в директории `.indirect`,
# в том числе и `docker-compose.yml`
# Использовать bash с опцией pipefail
# pipefail - фейлит выполнение пайпа, если команда выполнилась с ошибкой
SHELL=/bin/bash -o pipefail
# Останавливаем контейнеры и удаляем сеть
docker-kill:
docker-compose -f $${CI_JOB_ID:-.indirect}/docker-compose.yml kill
docker network rm network-$${CI_JOB_ID:-testrail} || true
# Предварительно выполняем docker-kill
docker-up: docker-kill
# Создаем сеть для окружения
docker network create network-$${CI_JOB_ID:-testrail}
# Забираем последние образы из docker-registry
docker-compose -f $${CI_JOB_ID:-.indirect}/docker-compose.yml pull
# Запускаем окружение
# force-recreate - принудительное пересоздание контейнеров
# renew-anon-volumes - не использовать volumes предыдущих контейнеров
docker-compose -f $${CI_JOB_ID:-.indirect}/docker-compose.yml up --force-recreate --renew-anon-volumes -d
# Ну и, на всякий случай, вывести что там у нас в принципе запущено на машинке
docker ps
# Коллектим логи сервисов
docker-logs:
mkdir ./logs || true
docker logs testrail-web-$${CI_JOB_ID:-local} >& logs/testrail-web.log
docker logs testrail-fpm-$${CI_JOB_ID:-local} >& logs/testrail-fpm.log
docker logs testrail-migration-$${CI_JOB_ID:-local} >& logs/testrail-migration.log
docker logs testrail-mysql-$${CI_JOB_ID:-local} >& logs/testrail-mysql.log
# Очистка раннера
docker-clean:
@echo Останавливаем все testrail-контейнеры
docker kill $$(docker ps --filter=name=testrail -q) || true
@echo Очистка докер контейнеров
docker rm -f $$(docker ps -a -f --filter=name=testrail status=exited -q) || true
@echo Очистка dangling образов
docker rmi -f $$(docker images -f "dangling=true" -q) || true
@echo Очистка testrail образов
docker rmi -f $$(docker images --filter=reference='registry.gitlab.com/touchbit/image/testrail/*' -q) || true
@echo Очистка всех неиспользуемых volume
docker volume rm -f $$(docker volume ls -q) || true
@echo Очистка всех testrail сетей
docker network rm $(docker network ls --filter=name=testrail -q) || true
docker ps
Bheka
yenza i-docker-up
$ make docker-up
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml kill
Killing testrail-web-local ... done
Killing testrail-fpm-local ... done
Killing testrail-mysql-local ... done
docker network rm network-${CI_JOB_ID:-testrail} || true
network-testrail
docker network create network-${CI_JOB_ID:-testrail}
d2ec063324081c8bbc1b08fd92242c2ea59d70cf4025fab8efcbc5c6360f083f
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml pull
Pulling db ... done
Pulling migration ... done
Pulling fpm ... done
Pulling web ... done
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml up --force-recreate --renew-anon-volumes -d
Recreating testrail-mysql-local ... done
Recreating testrail-fpm-local ... done
Recreating testrail-migration-local ... done
Recreating testrail-web-local ... done
docker ps
CONTAINER ID PORTS NAMES
a845d3cb0e5a 0.0.0.0:80->80/tcp, 0.0.0.0:443->443/tcp testrail-web-local
19d8ef001398 9000/tcp testrail-fpm-local
e28840a2369c 3306/tcp, 33060/tcp testrail-migration-local
0e7900c23f37 3306/tcp testrail-mysql-local
yenza ama-docker-logs
$ make docker-logs
mkdir ./logs || true
mkdir: cannot create directory ‘./logs’: File exists
docker logs testrail-web-${CI_JOB_ID:-local} >& logs/testrail-web.log
docker logs testrail-fpm-${CI_JOB_ID:-local} >& logs/testrail-fpm.log
docker logs testrail-migration-${CI_JOB_ID:-local} >& logs/testrail-migration.log
docker logs testrail-mysql-${CI_JOB_ID:-local} >& logs/testrail-mysql.log
Ilungiselela i-.gitlab-ci.yml
Isebenzisa izivivinyo zokuhlanganisa
Integration:
stage: test
tags:
- my-shell-runner
before_script:
# Аутентифицируемся в registry
- docker login -u gitlab-ci-token -p ${CI_JOB_TOKEN} ${CI_REGISTRY}
# Генерируем псевдоуникальные TR_HTTP_PORT и TR_HTTPS_PORT
- export TR_HTTP_PORT=$(shuf -i10000-60000 -n1)
- export TR_HTTPS_PORT=$(shuf -i10000-60000 -n1)
# создаем директорию с идентификатором задачи
- mkdir ${CI_JOB_ID}
# копируем в созданную директорию наш docker-compose.yml
# чтобы контекст был разный для каждой задачи
- cp .indirect/docker-compose.yml ${CI_JOB_ID}/docker-compose.yml
script:
# поднимаем наше окружение
- make docker-up
# запускаем тесты исполняемым jar (у меня так)
- java -jar itest.jar --http-port ${TR_HTTP_PORT} --https-port ${TR_HTTPS_PORT}
# или в контейнере
- docker run --network=testrail-network-${CI_JOB_ID:-local} --rm itest
after_script:
# собираем логи
- make docker-logs
# останавливаем окружение
- make docker-kill
artifacts:
# сохраняем логи
when: always
paths:
- logs
expire_in: 30 daysNjengomphumela wokuqhuba umsebenzi onjalo, uhla lwemibhalo lwamalogi kuma-artifact luzoqukatha isevisi namalogi okuhlola. Okuyinto elula kakhulu uma kwenzeka amaphutha. Isivivinyo ngasinye ngokuhambisana sibhala ilogi yaso, kodwa ngizokhuluma ngalokhu ngokwehlukana.
Ukuhlanza umgijimi
Umsebenzi uzokwethulwa ngokweshejuli kuphela.
stages:
- clean
- build
- test
Clean runner:
stage: clean
only:
- schedules
tags:
- my-shell-runner
script:
- make docker-cleanOkulandelayo, iya kuphrojekthi yethu ye-GitLab -> CI/CD -> Amashejuli -> Isheduli entsha bese wengeza uhlelo olusha.
Umphumela
Kwethulwa imisebenzi emi-4 ku-GitLab CI
Emalogi omsebenzi wokugcina nezivivinyo zokuhlanganisa sibona iziqukathi ezivela emisebenzini ehlukene
CONTAINER ID NAMES
c6b76f9135ed testrail-web-204645172
01d303262d8e testrail-fpm-204645172
2cdab1edbf6a testrail-migration-204645172
826aaf7c0a29 testrail-mysql-204645172
6dbb3fae0322 testrail-web-204645084
3540f8d448ce testrail-fpm-204645084
70fea72aa10d testrail-mysql-204645084
d8aa24b2892d testrail-web-204644881
6d4ccd910fad testrail-fpm-204644881
685d8023a3ec testrail-mysql-204644881
1cdfc692003a testrail-web-204644793
6f26dfb2683e testrail-fpm-204644793
029e16b26201 testrail-mysql-204644793
c10443222ac6 testrail-web-204567103
04339229397e testrail-fpm-204567103
6ae0accab28d testrail-mysql-204567103
b66b60d79e43 testrail-web-204553690
033b1f46afa9 testrail-fpm-204553690
a8879c5ef941 testrail-mysql-204553690
069954ba6010 testrail-web-204553539
ed6b17d911a5 testrail-fpm-204553539
1a1eed057ea0 testrail-mysql-204553539Ilogi enemininingwane eyengeziwe
$ docker login -u gitlab-ci-token -p ${CI_JOB_TOKEN} ${CI_REGISTRY}
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
WARNING! Your password will be stored unencrypted in /home/gitlab-runner/.docker/config.json.
Configure a credential helper to remove this warning. See
https://docs.docker.com/engine/reference/commandline/login/#credentials-store
Login Succeeded
$ export TR_HTTP_PORT=$(shuf -i10000-60000 -n1)
$ export TR_HTTPS_PORT=$(shuf -i10000-60000 -n1)
$ mkdir ${CI_JOB_ID}
$ cp .indirect/docker-compose.yml ${CI_JOB_ID}/docker-compose.yml
$ make docker-up
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml kill
docker network rm testrail-network-${CI_JOB_ID:-local} || true
Error: No such network: testrail-network-204645172
docker network create testrail-network-${CI_JOB_ID:-local}
0a59552b4464b8ab484de6ae5054f3d5752902910bacb0a7b5eca698766d0331
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml pull
Pulling web ... done
Pulling fpm ... done
Pulling migration ... done
Pulling db ... done
docker-compose -f ${CI_JOB_ID:-.indirect}/docker-compose.yml up --force-recreate --renew-anon-volumes -d
Creating volume "204645172_static-content" with default driver
Creating testrail-mysql-204645172 ...
Creating testrail-mysql-204645172 ... done
Creating testrail-migration-204645172 ... done
Creating testrail-fpm-204645172 ... done
Creating testrail-web-204645172 ... done
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
c6b76f9135ed registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 13 seconds ago Up 1 second 0.0.0.0:51148->80/tcp, 0.0.0.0:25426->443/tcp testrail-web-204645172
01d303262d8e registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 16 seconds ago Up 13 seconds 9000/tcp testrail-fpm-204645172
2cdab1edbf6a registry.gitlab.com/touchbit/image/testrail/migration:latest "docker-entrypoint.s…" 16 seconds ago Up 13 seconds 3306/tcp, 33060/tcp testrail-migration-204645172
826aaf7c0a29 mysql:5.7.22 "docker-entrypoint.s…" 18 seconds ago Up 16 seconds 3306/tcp testrail-mysql-204645172
6dbb3fae0322 registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 36 seconds ago Up 22 seconds 0.0.0.0:44202->80/tcp, 0.0.0.0:20151->443/tcp testrail-web-204645084
3540f8d448ce registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 38 seconds ago Up 35 seconds 9000/tcp testrail-fpm-204645084
70fea72aa10d mysql:5.7.22 "docker-entrypoint.s…" 40 seconds ago Up 37 seconds 3306/tcp testrail-mysql-204645084
d8aa24b2892d registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" About a minute ago Up 53 seconds 0.0.0.0:31103->80/tcp, 0.0.0.0:43872->443/tcp testrail-web-204644881
6d4ccd910fad registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" About a minute ago Up About a minute 9000/tcp testrail-fpm-204644881
685d8023a3ec mysql:5.7.22 "docker-entrypoint.s…" About a minute ago Up About a minute 3306/tcp testrail-mysql-204644881
1cdfc692003a registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" About a minute ago Up About a minute 0.0.0.0:44752->80/tcp, 0.0.0.0:23540->443/tcp testrail-web-204644793
6f26dfb2683e registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" About a minute ago Up About a minute 9000/tcp testrail-fpm-204644793
029e16b26201 mysql:5.7.22 "docker-entrypoint.s…" About a minute ago Up About a minute 3306/tcp testrail-mysql-204644793
c10443222ac6 registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 5 hours ago Up 5 hours 0.0.0.0:57123->80/tcp, 0.0.0.0:31657->443/tcp testrail-web-204567103
04339229397e registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 5 hours ago Up 5 hours 9000/tcp testrail-fpm-204567103
6ae0accab28d mysql:5.7.22 "docker-entrypoint.s…" 5 hours ago Up 5 hours 3306/tcp testrail-mysql-204567103
b66b60d79e43 registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 5 hours ago Up 5 hours 0.0.0.0:56321->80/tcp, 0.0.0.0:58749->443/tcp testrail-web-204553690
033b1f46afa9 registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 5 hours ago Up 5 hours 9000/tcp testrail-fpm-204553690
a8879c5ef941 mysql:5.7.22 "docker-entrypoint.s…" 5 hours ago Up 5 hours 3306/tcp testrail-mysql-204553690
069954ba6010 registry.gitlab.com/touchbit/image/testrail/web:latest "nginx -g 'daemon of…" 5 hours ago Up 5 hours 0.0.0.0:32869->80/tcp, 0.0.0.0:16066->443/tcp testrail-web-204553539
ed6b17d911a5 registry.gitlab.com/touchbit/image/testrail/fpm:latest "docker-php-entrypoi…" 5 hours ago Up 5 hours 9000/tcp testrail-fpm-204553539
1a1eed057ea0 mysql:5.7.22 "docker-entrypoint.s…" 5 hours ago Up 5 hours 3306/tcp testrail-mysql-204553539Yonke imisebenzi iqedwe ngempumelelo
Ama-artifacts omsebenzi aqukethe isevisi namalogi okuhlola
Konke kubonakala kukuhle, kodwa kune-nuance. Ipayipi lingakhanselwa ngenkani ngenkathi ukuhlolwa kokuhlanganisa kusebenza, lapho iziqukathi ezisebenzayo zingeke zimiswe. Ngezikhathi ezithile udinga ukuhlanza umgijimi. Ngeshwa, umsebenzi wokuthuthukiswa kwe-GitLab CE usesesimeni
Kodwa sengeze ukwethulwa komsebenzi ngokweshejuli, futhi akekho osenqabela ukuwuqhuba mathupha.
Iya kuphrojekthi yethu -> CI/CD -> Amashejuli bese uqhuba umsebenzi Clean runner
Inani:
- Sinomgijimi oyedwa wegobolondo.
- Akukho ukungqubuzana phakathi kwemisebenzi nendawo ezungezile.
- Senza imisebenzi enokuhlolwa kokuhlanganisa ngokuhambisana.
- Ungakwazi ukwenza izivivinyo zokuhlanganisa endaweni noma esitsheni.
- Isevisi kanye namalogi okuhlola aqoqwa futhi anamathiselwe emsebenzini wepayipi.
- Kungenzeka ukuhlanza umgijimi ezithombeni ezindala ze-Docker.
Isikhathi sokusetha amahora angu-2.
Yilokho kuphela, empeleni. Ngingajabula ukuthola impendulo.
Source: www.habr.com