blocks|key|2559568|text|您可以在旧版本中的“项目设置->+CI/CD管道->超时”或“项目设置->+Builds+->超时值”中设置全局超时。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2559569|从12.3版开始，您可以在CI+.yml文件中使用timeout设置每个阶段的超时|offset|length|style|CODE|2559570|timeout允许您为特定作业配置超时。例如：|blockquote|2559571|build:
++script:+build.sh
++timeout:+3+hours+30+minutes

test:
++script:+rspec
++timeout:+3h+30m|code-block|syntax|javascript|2559572|作业级超时可以超过项目级超时，但不能超过特定于Runner的超时。|2559573|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.gitlab.com/ee/ci/yaml/#timeout^0|0|P|7|P|7|0|0|0|7|0|0|0^^$0|@$1|2|3|4|5|6|7|Z|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|10|8|@$D|11|E|12|F|G]]|9|@$D|13|E|14|1|15]]|A|$]]|$1|H|3|I|5|J|7|16|8|@$D|17|E|18|F|G]]|9|@]|A|$]]|$1|K|3|L|5|M|7|19|8|@]|9|@]|A|$N|O]]|$1|P|3|Q|5|J|7|1A|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|Y]]]]

You can set a global timeout in &quot;Project settings -&gt; CI/CD Pipelines -&gt; Timeout&quot; or &quot;Project settings -&gt; Builds -&gt; Timeout&quot; in older versions.
As of version 12.3, you can set a timeout per stage in your CI .yml file using <a href="https://docs.gitlab.com/ee/ci/yaml/#timeout" rel="noreferrer"><code>timeout</code></a>:
<blockquote>
<code>timeout</code> allows you to configure a timeout for a specific job. For example:
</blockquote>
<pre><code>build:
 script: build.sh
 timeout: 3 hours 30 minutes

test:
 script: rspec
 timeout: 3h 30m
</code></pre>
<blockquote>
The job-level timeout can exceed the project-level timeout but can’t exceed the Runner-specific timeout.
</blockquote>

blocks|key|1805436|text|可以设置两个超时：项目超时和运行超时。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1805437|项目超时：|1805438|可以从设置+->+CI/CD+->+通用管道设置每个作业的超时时间|1805439|​|1805440|📷|atomic|1805441|1805442|运行超时：|1805443|跑步者的超时可以从Settings+->+CI/CD+->+Runners中设置，从为该项目激活的运行程序中选择runner，并从runner编辑表单中编辑最大作业超时时间。|1805444|1805445|1805446|请注意，这两种类型的超时可以被对方覆盖。请参考文档。|1805447|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://developer.qcloudimg.com/http-save/yehe-900000/bb104cd94a7189c193c5c072d66ea981.png|imageAlt|1|https://developer.qcloudimg.com/http-save/yehe-900000/396ab8634fa5ba6ff112fbf1bb336524.png|2|LINK|MUTABLE|url|https://docs.gitlab.com/ee/ci/runners/#setting-maximum-job-timeout-for-a-runner^0|9|4|E|4|0|0|5|0|3|2|9|5|I|4|0|0|0|1|0|0|0|0|5|0|9|8|L|5|U|7|1D|12|0|0|1|0|1|1|0|0|1|0|0|Q|N|2|2|0^^$0|@$1|2|3|4|5|6|7|1D|8|@$9|1E|A|1F|B|C]|$9|1G|A|1H|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1I|8|@$9|1J|A|1K|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|1L|8|@$9|1M|A|1N|B|C]|$9|1O|A|1P|B|C]|$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1S|8|@]|D|@]|E|$]]|$1|L|3|M|5|N|7|1T|8|@]|D|@$9|1U|A|1V|1|1W]]|E|$]]|$1|O|3|K|5|6|7|1X|8|@]|D|@]|E|$]]|$1|P|3|Q|5|6|7|1Y|8|@$9|1Z|A|20|B|C]]|D|@]|E|$]]|$1|R|3|S|5|6|7|21|8|@$9|22|A|23|B|C]|$9|24|A|25|B|C]|$9|26|A|27|B|C]|$9|28|A|29|B|C]]|D|@]|E|$]]|$1|T|3|M|5|N|7|2A|8|@$9|2B|A|2C|B|C]]|D|@$9|2D|A|2E|1|2F]]|E|$]]|$1|U|3|K|5|6|7|2G|8|@$9|2H|A|2I|B|C]]|D|@]|E|$]]|$1|V|3|W|5|6|7|2J|8|@$9|2K|A|2L|B|C]]|D|@$9|2M|A|2N|1|2O]]|E|$]]|$1|X|3|-4|5|6|7|2P|8|@]|D|@]|E|$]]]|Y|$Z|$5|10|11|12|E|$13|14|15|-4]]|16|$5|10|11|12|E|$13|17|15|-4]]|18|$5|19|11|1A|E|$1B|1C]]]]

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

<a href="https://i.stack.imgur.com/4Q9Oa.png" rel="noreferrer"><img src="https://i.stack.imgur.com/4Q9Oa.png" alt="enter image description here"></a>

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. 
<a href="https://i.stack.imgur.com/RQwJ5.png" rel="noreferrer"><img src="https://i.stack.imgur.com/RQwJ5.png" alt="enter image description here"></a>

Be aware that these two types of timeout can be overridden by each other. Refer the <a href="https://docs.gitlab.com/ee/ci/runners/#setting-maximum-job-timeout-for-a-runner" rel="noreferrer">docs</a>.

blocks|key|2559689|text|在Gitlab+12.3中引入了一个特定于作业的超时|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2559690|https://docs.gitlab.com/ce/ci/yaml/README.html#timeout|offset|length|2559691|build:
++script:+build.sh
++timeout:+3+hours+30+minutes

test:
++script:+rspec
++timeout:+3h+30m|code-block|syntax|javascript|2559692|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|1I|0|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|H|7|W|8|@]|9|@]|A|$I|J]]|$1|K|3|-4|5|6|7|X|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|C]]]]

A job-specific timeout was introduced in Gitlab 12.3

<a href="https://docs.gitlab.com/ce/ci/yaml/README.html#timeout" rel="noreferrer">https://docs.gitlab.com/ce/ci/yaml/README.html#timeout</a>

<pre><code>build:
 script: build.sh
 timeout: 3 hours 30 minutes

test:
 script: rspec
 timeout: 3h 30m
</code></pre>

blocks|key|1307516|text|如果在Gitlab运行它，那么上面所述的答案已经告诉了正确的方法。但是，如果您想在本地运行Gitlab+CI，也可以使用自己的运行器运行，那么运行超时时您需要传递命令。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1307517|gitlab-runner码头job_name+--超时3600|1307518|这里，它将跑步者超时设置为3600秒。|1307519|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If running it at Gitlab, then the above stated answers has already told the right way. But if you would like to run the Gitlab CI locally that too with tour own runner, then runners timeout you need to pass with command. 

gitlab-runner exec docker job_name --timeout 3600

here it is setting runners timeout as 3600 seconds

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

<blockquote>
<pre><code>ERROR: Build failed: execution took longer than 3600 seconds
</code></pre>
</blockquote>

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

GitLab CI Pipeline Stage Timeout

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我正在使用一个自我托管的GitLab CI server (社区版本v8.9.5)和gitlab-ci-multi-runner 1.2.0来构建一个项目。我的一个管道阶段(测试)需要一段时间才能运行，我得到以下erm：错误:生成失败:执行时间超过3600秒我该把这个超时的覆盖放哪里？我能把它应用到测试管道阶段吗？

问GitLab CI流水线级超时
EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问GitLab CI流水线级超时EN

回答 4

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问GitLab CI流水线级超时
EN