🥇GitLab Imbaleki yeShell. Ukuqaliswa okukhuphisanayo kweenkonzo ezivavanyiweyo usebenzisa iDocker Compose

Eli nqaku liza kuba nomdla kubo bobabini abavavanyi kunye nabaphuhlisi, kodwa lijoliswe ikakhulu kwiingcali ezizenzekelayo ezijongene nengxaki yokumisela i-GitLab CI / CD yokuvavanya ukudibanisa kwiimeko zokungonelanga kwezibonelelo kunye / okanye ukungabikho kwesitya. iqonga leokhestra. Ndiza kukuxelela indlela yokuseta ukusasazwa kweemeko zovavanyo usebenzisa i-docker qamba kwimbaleki enye ye-GitLab yeqokobhe kwaye ukuze xa uhambisa iindawo ezininzi, iinkonzo ezisungulweyo zingaphazamisi enye kwenye.

Iziqulatho

Izinto ezifuneka kuqala
GitLab Shell Imbaleki
Ukulungiselela i-docker-compose.yml
Ukulungiselela iMakefile
Ukulungiselela .gitlab-ci.yml
- Ukuqhuba iimvavanyo zokudibanisa
- Ukucoca imbaleki
Isiphumo

Izinto ezifuneka kuqala

Kwimeko yam, kuye kwenzeka ukuba uvavanyo lokudibanisa "luphathwe" kwiiprojekthi. Kwaye kaninzi ingxaki yokuqala kunye neyona nto ibalulekileyo ngumbhobho weCI, apho uvavanyo lokudibanisa kuphuhliswa Iinkonzo (ii) zenziwa kwindawo yedev/yenqanaba. Oku kubangele iingxaki ezininzi:
- Ngenxa yeziphene kwinkonzo ethile ngexesha lokuvavanya ukudibanisa, isiphaluka sovavanyo singonakaliswa yidatha ephukileyo. Kwakukho iimeko xa kuthunyelwa isicelo ngefomathi eyaphukileyo ye-JSON iphazamise inkonzo, eyenza ukuba i-stand ingasebenzi ngokupheleleyo.
- Ukucotha kwesekethe yovavanyo njengoko idatha yovavanyo isanda. Ndicinga ukuba akukho ngqiqweni ukuchaza umzekelo ngokucoca / ukubuyisela umva isiseko sedatha. Kwinkqubo yam, andizange ndidibane neprojekthi apho le nkqubo ihambe kakuhle.
- Umngcipheko wokuphazamisa ukusebenza kwesekethe yovavanyo xa uvavanya izicwangciso zesistim jikelele. Umzekelo, umsebenzisi/iqela/igama lokugqithisa/umgaqo-nkqubo wesicelo.
- Idatha yovavanyo evela kuvavanyo oluzenzekelayo yenza ubomi bube nzima kubavavanyi bezandla.
Abanye baya kuthi ii-autotes ezilungileyo kufuneka zicoce idatha emva kwabo. Ndineengxoxo ezichaseneyo:
- Iimpawu zeDynamic zikulungele kakhulu ukuzisebenzisa.
- Ayizizo zonke izinto ezinokususwa kwinkqubo nge-API. Umzekelo, umnxeba wokucima into awuzange uphunyezwe kuba uphikisana nengqiqo yeshishini.
- Xa udala into nge-API, isixa esikhulu semetadata sinokudalwa, okuyingxaki ukuyicima.
- Ukuba iimvavanyo zixhomekeke phakathi kwazo, ngoko inkqubo yokucoca idatha emva kokuqhuba iimvavanyo ijika ibe yintloko.
- Okongeziweyo (kwaye, ngokombono wam, akuchanekanga) iifowuni kwi-API.
- Kwaye ingxabano ephambili: xa idatha yovavanyo iqala ukucocwa ngokuthe ngqo kwisiseko sedatha. Oku kujika kube yisekisi yokwenyani yePK/FK! Siva kubaphuhlisi: "Ndisandula ukongeza / ndilususile / ndiluthiye ngokutsha uphawu, kutheni le nto iimvavanyo zokudityaniswa ezingama-100500 zibanjiwe?"
Ngokombono wam, esona sisombululo sifanelekileyo yindawo eguqukayo.
Abantu abaninzi basebenzisa i-docker-compose ukuqhuba indawo yovavanyo, kodwa bambalwa abantu abasebenzisa i-docker-compose xa beqhuba uvavanyo lokudibanisa kwi-CI/CD. Kwaye apha andithatheli ngqalelo i-kubernetes, i-swarm kunye nezinye iiplatifti ze-orchestration. Ayizizo zonke iinkampani ezinazo. Kuya kuba kuhle ukuba i-docker-compose.yml ibikwindawo yonke.
Nokuba sineyethu imbaleki ye-QA, sinokuqiniseka njani ukuba iinkonzo eziqaliswe nge-docker-compose aziphazamisani?
Indlela yokuqokelela iilogi zeenkonzo ezivavanyiweyo?
Indlela yokucoca umgijimi?

Ndinembaleki yam yeGitLab yeeprojekthi zam kwaye ndiye ndadibana nale mibuzo ngexesha lophuhliso Umxhasi weJava kuba TestRail. Ngokuchanekileyo, xa uqhuba iimvavanyo zokudibanisa. Ngezantsi siza kusombulula le miba sisebenzisa imizekelo evela kule projekthi.

Kumxholo

GitLab Shell Imbaleki

Kumgijimi, ndincoma umatshini we-Linux we-virtual kunye ne-4 vCPU, i-4 GB RAM, i-50 GB HDD.
Kukho ulwazi oluninzi malunga nokuseta i-gitlab-runner kwi-Intanethi, ngokufutshane:

Ngena kumatshini nge-SSH
Ukuba ungaphantsi kwe-8 GB RAM, ngoko ndincoma yenza utshintsho 10 GBukuze umbulali we-OOM angezi aze abulale imisebenzi yethu ngenxa yokunqongophala kwe-RAM. Oku kunokwenzeka xa imisebenzi engaphezu kwemi-5 iqaliswa ngaxeshanye. Imisebenzi iya kuqhubeka ngokucothayo, kodwa ngokuthe chu.

Umzekelo kunye nombulali we-OOM

Ukuba ubona kwiilog zomsebenzi bash: line 82: 26474 Killed, emva koko uphumeze kwimbaleki sudo 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:0kB
```
Kwaye ukuba umfanekiso ujongeka ngolu hlobo, ngoko yongeza ukutshintsha okanye ukongeza i-RAM.

Faka ifayile gitlab-imbaleki, docker, Dibanisa idokhethi, yenza.

Ukongeza umsebenzisi gitlab-runner kwiqela docker

sudo groupadd docker
sudo usermod -aG docker gitlab-runner

Bhalisa gitlab-imbaleki.
Vula ukuhlelwa /etc/gitlab-runner/config.toml kwaye wongeze
```
concurrent=20
[[runners]]
  request_concurrency = 10
```
Oku kuya kukuvumela ukuba wenze imisebenzi ehambelanayo kwimbaleki enye. Funda ngokugqithisileyo apha.
Ukuba unomatshini onamandla ngakumbi, umzekelo 8 vCPU, 16 GB RAM, ke la manani angenziwa ubuncinane amaxesha ama-2 amakhulu. Kodwa konke kuxhomekeke ekubeni yintoni kanye eza kuqaliswa kule mbaleki kwaye ngowuphi ubungakanani.

Kwanele.

Kumxholo

Ukulungiselela i-docker-compose.yml

Umsebenzi oyintloko yi-universal docker-compose.yml, apho abaphuhlisi/abavavanyi banokusebenzisa zombini kwindawo kunye nakwipayipi yeCI.

Okokuqala, senza amagama enkonzo awodwa kwiCI. Enye yezinto eziguquguqukayo ezizodwa kwi-GitLab CI kukuguquguquka CI_JOB_ID. Ukuba uyachaza container_name ngentsingiselo "service-${CI_JOB_ID:-local}", ngoko kwimeko:

ukuba CI_JOB_ID ayichazwanga kutshintsho lwemo engqongileyo,
ke igama lenkonzo liya kuba service-local
ukuba CI_JOB_ID ichazwe kwizinto ezahlukeneyo zemo engqongileyo (umzekelo 123),
ke igama lenkonzo liya kuba service-123

Okwesibini, senza inethiwekhi eqhelekileyo kwiinkonzo eziqalisiwe. Oku kusinika ukwahlula kwinqanaba lothungelwano xa siqhuba iimeko-bume zovavanyo ezininzi.

networks:
  default:
    external:
      name: service-network-${CI_JOB_ID:-local}

Ngokwenyani, eli linyathelo lokuqala kwimpumelelo =)

Umzekelo we-docker-compose.yml yam kunye nezimvo

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:
      - default

Umzekelo wokuqhutywa 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       ... done

Kodwa ayizizo zonke izinto ezilula kakhulu ngokusungulwa kwi-CI.

Kumxholo

Ukulungiselela iMakefile

Ndisebenzisa i-Makefile kuba ilula kakhulu kulawulo lwendawo yendawo kunye nakwiCI. Amagqabantshintshi angakumbi kwi-intanethi

# У меня в проектах все вспомогательные вещи лежат в директории `.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

Jonga

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 i-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

Kumxholo

Ukulungiselela .gitlab-ci.yml

Ukuqhuba iimvavanyo zokudibanisa

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 days

Njengomphumo wokuqhuba umsebenzi onjalo, uvimba weefayili welog kwi-artifacts uya kuqulatha iinkonzo kunye neelog zovavanyo. Eyona nto ilunge kakhulu xa kukho iimpazamo. Uvavanyo ngalunye ngokuhambelanayo lubhala ilogi yalo, kodwa ndiza kuthetha ngale nto ngokwahlukileyo.

Kumxholo

Ukucoca imbaleki

Umsebenzi uya kuphehlelelwa kuphela ngokweshedyuli.

stages:
- clean
- build
- test

Clean runner:
  stage: clean
  only:
    - schedules
  tags:
    - my-shell-runner
  script:
    - make docker-clean

Okulandelayo, yiya kwiprojekthi yethu yeGitLab -> CI/CD -> Iishedyuli-> Ishedyuli eNtsha kwaye wongeze ishedyuli entsha

Kumxholo

Isiphumo

Ukuqaliswa kwemisebenzi emi-4 kwi-GitLab CI

Kwiilogi zomsebenzi wokugqibela kunye neemvavanyo zokudibanisa sibona izitya ezivela kwimisebenzi eyahlukeneyo

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-204553539

Ilog eneenkcukacha ezininzi

$ 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-204553539

Yonke imisebenzi igqitywe ngempumelelo

Izinto zakudala zomsebenzi ziqulathe inkonzo kunye neelog zovavanyo

Yonke into ibonakala intle, kodwa kukho i-nuance. Umbhobho unokurhoxiswa ngenkani ngelixa uvavanyo lohlanganiso luqhuba, apho izikhongozeli eziqhubayo aziyi kunqunyanyiswa. Ukususela ngamaxesha kufuneka uhlambulule umgijimi. Ngelishwa, umsebenzi wokuphucula kwi-GitLab CE usekwimo vula

Kodwa songeze ukuqaliswa komsebenzi ngokweshedyuli, kwaye akukho mntu usithintelayo ukuba siwuqhube ngesandla.
Yiya kwiprojekthi yethu -> CI/CD -> Iishedyuli kwaye uqhube umsebenzi Clean runner

Iyonke:

Sinembaleki enye yeqokobhe.
Akukho ngquzulwano phakathi kwemisebenzi kunye nokusingqongileyo.
Siqhuba imisebenzi kunye novavanyo lokudibanisa ngokuhambelanayo.
Ungaqhuba iimvavanyo zohlanganiso kwindawo okanye kwisikhongozeli.
Iinkonzo kunye neelog zovavanyo ziqokelelwa kwaye ziqhotyoshelwe kumsebenzi wombhobho.
Kuyenzeka ukucoca imbaleki kwimifanekiso yakudala yeDocker.

Ixesha lokumisela ~iiyure ezi-2.
Yiloo nto kuphela, eneneni. Ndingavuya ukufumana impendulo.

Kumxholo

umthombo: www.habr.com

GitLab Shell Imbaleki. Ukuqaliswa okukhuphisanayo kweenkonzo ezivavanyiweyo kusetyenziswa iDocker Compose

Iziqulatho

Izinto ezifuneka kuqala

GitLab Shell Imbaleki

Ukulungiselela i-docker-compose.yml

Ukulungiselela iMakefile

Ukulungiselela .gitlab-ci.yml

Ukuqhuba iimvavanyo zokudibanisa

Ukucoca imbaleki

Isiphumo

Yongeza izimvo Phendula impendulo