That runs jobs on the runner, can access anyone else’s code that runs on the With shared runners, this means that anyone
SECRET LODE RUNNER 2 LEVELS FULL
If you can run a job on the runner, you can get full access to the file system,Īnd thus any code it runs as well as the token of the runner. The job, if running longer, times out after 30 minutes Be careful with sensitive information.You set the maximum job timeout for a runner to 30 minutes.You remove the maximum job timeout configuration from a runnerĮxample 3 - Runner timeout smaller than project timeout.The job, if running longer, times out after 2 hoursĮxample 2 - Runner timeout not configured.You set the CI/CD Timeout for a project to 2 hours.You set the maximum job timeout for a runner to 24 hours.If notĭefined, the project’s job timeout settingĮxample 1 - Runner timeout bigger than project timeout Enter a value under Maximum job timeout.Select your specific runner to edit the settings.In a project, go to Settings > CI/CD > Runners.
On, you cannot override the job timeout for shared runners and must use the project defined timeout. This feature can be used to prevent your shared runner from being overwhelmedīy a project that has jobs with a long timeout (for example, one week). If smaller than the project defined timeout, takes precedence. Set maximum job timeout for a runnerįor each runner, you can specify a maximum job timeout. If you need to configure runners on the machine where you installed GitLab Runner, see If you have installed your own runners, you can configure and secure them in GitLab.