Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
57b999ed
Commit
57b999ed
authored
Jan 14, 2021
by
Cleveland Bledsoe Jr
Committed by
Suzanne Selhorn
Jan 14, 2021
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add explicit instructions for maximum job timeout
parent
cd79e3c1
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
9 additions
and
0 deletions
+9
-0
doc/ci/runners/README.md
doc/ci/runners/README.md
+9
-0
No files found.
doc/ci/runners/README.md
View file @
57b999ed
...
...
@@ -269,6 +269,15 @@ by a project that has jobs with a long timeout (for example, one week).
When not configured, runners do not override the project timeout.
On GitLab.com, you cannot override the job timeout for shared runners and must use the
[
project defined timeout
](
../pipelines/settings.md#timeout
)
.
To set the maximum job timeout:
1.
In a project, go to
**Settings > CI/CD > Runners**
.
1.
Select your specific runner to edit the settings.
1.
Enter a value under
**Maximum job timeout**
.
1.
Select
**Save changes**
.
How this feature works:
**Example 1 - Runner timeout bigger than project timeout**
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment