帶有2名工人的gitlab跑步者：第1名工人（BE）很好，第2名工人（FE）使用docker而不是shell

首先，我為 1 份作業設定了 1 名工人。為 API 部署我的后端。

我使用“shell”作為執行者。.toml 檔案是這樣的結構：

concurrent = 1
check_interval = 0

[session_server]
   session_timeout = 1800

[[runners]]
  name = "Gitlab Runner Josere Backend"
  url = "https://gitlab.com/"
  token = "sOmEtOkeN1G0Tfr0mGitlab"
  executor = "shell"
  [runners.custom_build_dir]
  [runners.cache]
    [some mumbo jumbo about caching.. does it matter?]

經過一番努力，我得到了這個 .gitlab-ci.yml 的正常作業：

deploy-production:
  stage: deploy
  variables:
    GIT_STRATEGY: clone
  script:
    - cd ./lumen/
    - composer install
    - sudo cp -r $CI_PROJECT_DIR/lumen/. /home/josere/public_html/api/
    - sudo cp /home/josere/env/.env /home/josere/public_html/api

這是運行器的執行輸出：

Running with gitlab-runner 15.2.1 (32fc1585)
  on Gitlab Runner Josere backend 9JxGrMLz
Preparing the "shell" executor
00:00
Using Shell executor...
Preparing environment
00:00
Running on ####[my server]#####...
Getting source from Git repository
00:03
Fetching changes with git depth set to 50...
Initialized empty Git repository in /home/gitlab-runner/builds/9JxGrMLz/0/paspalas/josere/.git/
Created fresh repository.
... etc ...

在 Gitlab 的前端存盤庫中，我使用了相同的跑步者設定。我無法真正安裝跑步者（我猜它已經在運行），但我可以復制那里顯示的令牌。

然后我根據來自 gitlab 的這個檔案更改了我的 .toml 檔案（https://docs.gitlab.com/runner/fleet_scaling/）：

concurrent = 2
check_interval = 0

[session_server]
   session_timeout = 1800

[[runners]]
  name = "Gitlab Runner Josere Backend"
  url = "https://gitlab.com/"
  token = "sOmEtOkeN1G0Tfr0mGitlab"
  executor = "shell"
  [runners.custom_build_dir]
  [runners.cache]
    [some mumbo jumbo about caching.. does it matter?]

[[runners]]
  name = "Gitlab Runner Josere Frontend"
  url = "https://gitlab.com/"
  token = "TheOtherTokenThatIgotFromFrontendRepo!"
  executor = "shell"
  [runners.custom_build_dir]
  [runners.cache]
    [some mumbo jumbo about caching.. does it matter?]

請注意，我確實將執行者保持在“shell”上。這是 .gitlab-ci.yml 的腳本，它位于前端 repo 的根目錄中：

deploy-production:
  stage: deploy
  variables:
    GIT_STRATEGY: clone
  script:
    - npm install
    - npm run build
    - sudo cp -r $CI_PROJECT_DIR/public/. /home/josere/public_html/

但是當我提交我的前端并檢查作業人員的（失敗）日志時，它會這樣寫：

Running with gitlab-runner 15.4.0~beta.5.gdefc7017 (defc7017)
  on green-1.shared.runners-manager.gitlab.com/default JLgUopmM
Preparing the "docker machine" executor
00:06
Using Docker executor with image ruby:2.5 ...
Pulling docker image ruby:2.5 ...
Using docker image sha256:27d###mumbojumbo###2383b for ruby:2.5 with digest ruby@sha256:ecc3###mumbojumbo###444b ...
Preparing environment
00:00
Running on runner-jlguopmm-project-39467125-concurrent-0 via runner-jlguopmm-shared-1665674167-6adf45bf...
Getting source from Git repository
00:02
$ eval "$CI_PRE_CLONE_SCRIPT"
Fetching changes with git depth set to 20...
Initialized empty Git repository in /builds/paspalas/josere-frontend/.git/
Created fresh repository.
Checking out c39e641c as materialui...
Skipping Git submodules setup
Executing "step_script" stage of the job script
00:01
Using docker image sha256:27d###mumbojumbo###3b for ruby:2.5 with digest ruby@sha256:ecc3e###mumbojumbo####44b ...
$ sudo npm install
/bin/bash: line 126: sudo: command not found
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1

顯然，似乎有很多事情出錯了，首先：為什么它使用 docker 而我明確告訴它是“shell”？

uj5u.com熱心網友回復：

我解決了這個問題。盡管 GitLab 的檔案區分了“跑步者”和“作業”，但 gitlab-runner 稱這些“跑步者”的“注冊”。我像這樣進行了（額外的）注冊：

- gitlab-runner register
[filling in info]
- nano /etc/gitlab-runner/config.toml
[check if you have the additional runner]
- gitlab-runner run
[according to gitlab-runner help this is to fire up multiple runners]
- gitlab-runner list
[ now you can check if all "runners" (jobs) are running]

標籤：壳GitLab持续集成gitlab-cigitlab-ci-runner

上一篇：為什么grep找不到以下劃線開頭的單詞

下一篇：為驗證集創建滯后