Skip to content

Update maximum job timeout UI text

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Details

The maximum job timeout field when creating a runner is in seconds. When you add a max timeout value, it must be at least 10 minutes, but the user has to manually calculate minutes to seconds. It also isn't clear what it means if you leave the job timeout blank.

Maximum job timeout

Maximum amount of time the runner can run before it terminates. If a project has a shorter job timeout period, the job timeout period of the instance runner is used instead.

Enter the job timeout in seconds. Must be a minimum of 600 seconds.

Proposal

  • Update error message to be in seconds.
  • Update the form field text to use the following:

Maximum job timeout

Maximum amount of time the runner can run before it terminates. The job timeout of the runner is used if it is shorter than the project job timeout. For example, if the maximum job timeout for a runner is 30 minutes, but the CI/CD timeout for a project is 2 hours, the job running in that project times out after 30 minutes.

[ 👉 Form field goes here 👈 ]

Enter number of seconds. Must be 600 seconds or more. If not defined, the runner uses the project job timeout value.

Edited by 🤖 GitLab Bot 🤖