我们已经设置了Gitlab自动缩放主机,如中所述
official docs
.
gitlab runner实例工作正常,由gitlab识别。org,并成功生成运行人员来执行作业。
然而,这些工作并没有真正从繁殖的跑步者开始。他们坚持在这一点上。
我们打开了调试级日志记录,唯一看起来不高兴的消息是这些重复的消息:
msg="Failed to request job: runner requestConcurrency meet"
配置。toml看起来像这样:
concurrent = 20
check_interval = 10
log_level = "debug"
log_format = "text"
[session_server]
session_timeout = 1800
[[runners]]
name = "gitlab-runner-master"
url = "https://gitlab.com/"
token = "blabla"
executor = "docker+machine"
limit = 25
[runners.custom_build_dir]
[runners.cache]
Type = "s3"
Shared = true
[runners.cache.s3]
ServerAddress = "s3.amazonaws.com"
AccessKey = "blabla"
SecretKey = "blabla"
BucketName = "gitlab.cache.dyynamo.net"
BucketLocation = "us-east-1"
[runners.cache.gcs]
[runners.cache.azure]
[runners.docker]
tls_verify = false
image = "amd64/ubuntu:16.04"
privileged = true
disable_entrypoint_overwrite = false
oom_kill_disable = false
disable_cache = true
volumes = ["/cache"]
shm_size = 0
[runners.machine]
IdleCount = 0
IdleTime = 600
MaxBuilds = 100
MachineDriver = "amazonec2"
MachineName = "gitlab-docker-machine-%s"
你知道问题出在哪里吗?
也注意到
this still-open similar issue
.