Gitlab CI作业随机失败/通过 [英] Gitlab CI jobs fail/pass randomly

问题描述

对于要部署的某些项目，我有一些 gitlab-ci.yml 文件。在将我的头撞在墙上几个小时之后，我意识到它们随机通过/失败。当然，没有任何变化，只需按一下重试按钮，有时作业就会通过，而有时作业会失败。

I have some gitlab-ci.yml files for some projects that I want to deploy. After banging my head against the wall for several hours, I've realized that they pass/fail randomly. Of course, nothing changes, it's just a matter of pressing on the "Retry" button and sometimes the job will pass and other times it will fail.

这是<我正在使用的code> .gitlab-ci.yml ：

image: docker:latest

services:
  - docker:dind

before_script:
  - echo "Runnig before_script"
  - apk add --no-cache py-pip python-dev libffi-dev openssl-dev gcc libc-dev make
  - pip install docker-compose

stages:
  - test
  - build
  - deploy

test:
  stage: test
  script:
    - echo "Testing the app"
    - docker-compose run app sh -c "python /app/manage.py test && flake8"

build:
  stage: build
  only:
    - develop
    - production
    - feature/deploy-debug-gitlab

  script:
    - echo "Building the app"
    - docker-compose build

deploy:
  stage: deploy
  only:
    - master
    - feature/deploy
  script:
    - echo "Deploying the app"
    - docker-compose up -d
  environment: production
  when: manual

我在那做错了吗？

工作失败 时，我总是会收到错误： apk命令未找到。像这样：

Running with gitlab-runner 11.11.1 (5a147c92)
  on My Runner Jd5HNvxy
Using Shell executor...
Running on ubuntu-512mb-lon1-01...
Reinitialized existing Git repository in /home/gitlab-runner/builds/Jd5HNvxy/0/<my.name>/<my.app>/.git/
Fetching changes...
Checking out 3f388ce6 as feature/deploy...
Skipping Git submodules setup
$ echo "Runnig before_script"
Runnig before_script
$ apk add --no-cache py-pip python-dev libffi-dev openssl-dev gcc libc-dev make
bash: line 88: apk: command not found
ERROR: Job failed: exit status 1

，我明白了：

When the job passes, I get this:

Running with gitlab-runner 11.11.1 (5a147c92)
  on docker-auto-scale fa6cab46
Using Docker executor with image docker:latest ...
Starting service docker:dind ...
Pulling docker image docker:dind ...
Using docker image sha256:bed64de70fa1f4d0b5a498791647c45d954cb0306ec2852dbcfb956f4ff3b0d6 for docker:dind ...
Waiting for services to be up and running...
Pulling docker image docker:latest ...
Using docker image sha256:af42f41a7d73a4a181843011f62cbdefa6d0f546bc7b50f71163750e0475a928 for docker:latest ...
Running on runner-fa6cab46-project-12561543-concurrent-0 via runner-fa6cab46-srm-1559293461-381b8d99...
Initialized empty Git repository in /builds/<my.name>/<my.app>/.git/
Fetching changes...
Created fresh repository.
From https://gitlab.com/<my.name>/<my.app>
 * [new branch]      develop        -> origin/develop
 * [new branch]      feature/deploy -> origin/feature/deploy
 * [new branch]      master         -> origin/master
Checking out 3f388ce6 as feature/deploy...

Skipping Git submodules setup
$ echo "Runnig before_script"
Runnig before_script
$ apk add --no-cache py-pip python-dev libffi-dev openssl-dev gcc libc-dev make
fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/main/x86_64/APKINDEX.tar.gz
fetch http://dl-cdn.alpinelinux.org/alpine/v3.9/community/x86_64/APKINDEX.tar.gz
(1/30) Installing binutils (2.31.1-r2)
(2/30) Installing gmp (6.1.2-r1)
(3/30) Installing isl (0.18-r0)
...
...
...

推荐答案

发生这种情况是因为您拥有不同的跑步者，我的跑步者Jd5HNvxy和 docker-auto-scale fa6cab46。

This happens because you have different runners, „My Runner Jd5HNvxy" and „docker-auto-scale fa6cab46". Your job is being executed by whichever runner is faster to grab the job.

在失败的情况下，您的工作将在标记为 shell executor的运行程序上运行，然后运行一个ubuntu系统-在日志中可见。 Ubuntu不附带apk命令，因此作业失败。

In your failing case, your job runs on a runner marked as „shell executor", running on an ubuntu system - visible in the logs. Ubuntu does not ship with the apk command, therefore the job fails.

但是您的其他运行程序使用 docker执行程序，因此提取docker映像并运行

Your other runner, however, uses the „docker" executor, therefore pulling the docker image and running the job without issues.

可能的解决方案：

• 删除/暂停shell运行器


• 使跑步者成为特定跑步者，并将其手动分配给项目。


• 为跑步者添加标签，例如 shell和 docker。然后，在CI配置中，声明使用正确标记的运行器。有关更多信息，请参见官方文档： https：//docs.gitlab。 com / ce / ci / yaml / README.html＃tags

• Remove/pause the shell runner.
• Make your runners „specific" runners and assign them to the projects manually.
• Add tags to your runners, e.g. „shell" and „docker". Then, in the CI config, declare to use a properly tagged runner. See the official docs for more info: https://docs.gitlab.com/ce/ci/yaml/README.html#tags

这篇关于Gitlab CI作业随机失败/通过的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！