GitLab CI Pipeline Stage Timeout

问题:

I'm using a self-hosted GitLab CI server (community edition v8.9.5) and gitlab-ci-multi-runner 1.2.0 to build a project. One of my pipeline stages (test) takes a while to run and I get the following erm:

ERROR: Build failed: execution took longer than 3600 seconds

Where do I put the override for this timeout? Can I apply it to just the test pipeline stage?

回答1:

This is set in GitLab. See "Project settings -> CI/CD Pipelines -> Timeout" or "Project settings -> Builds -> Timeout" in older versions.

I'm afraid it's not possible to set it per stage or job.

回答2:

There are two timeout can be set: project timeout and runner timeout.

Project timeout:

It is possible to set timeout per job from Settings -> CI/CD -> General pipelines

Runner timeout:

runner's timeout can be set from Settings -> CI/CD -> Runners, select the runner from Runners activated for this project and edit the Maximum job timeout from the runner edit form.

Be aware that these two types of timeout can be overridden by each other. Refer the docs.