#Git submodule set branch full#
#Git submodule set branch registration#
#Git submodule set branch code#

Expand the General pipelines settings section.

That new runner may then be used to obtain the values of secret variables or to clone project code.

#Git submodule set branch registration#

A registration token can be used to register another runner for the project. If you think that a registration token for a project was revealed, you should Reset the runner registration token for a project We’re always looking for contributions that can mitigate these Mentioned briefly earlier, but the following things of runners can be exploited.

If shared runners are disabled on the forked project, then this should also be disabled on the new namespace.

If shared runners are enabled on the forked project, then this should also be enabled on the new namespace.

To work around this issue, you should make sure that the shared runner settings are consistent in the forked project and the new namespace. if the runner settings of the project you are forking does not match the new project namespace. Someone forks that project, the shared runners serve jobs of this project.īecause of a known issue, you might encounter the message An error occurred while forking the project. This means that if you have shared runners set up for a project and Whenever a project is forked, it copies the settings of the jobs that relate

Find the runner you want to protect or unprotect.

Go to the project’s Settings > CI/CD and expand the Runners section.

Protected branches or protected tags only, When a runner is protected, the runner picks jobs created on You can protect runners so they don’t reveal sensitive information. Prevent runners from revealing sensitive information On large public GitLab instances, controlling access to your GitLab instance,Īnd using more secure runner executors. The above is easily avoided by restricting the usage of shared runners To create a clone of a runner and submit false jobs, for example. In addition, because you can get access to the runner token, it is possible

#Git submodule set branch code#

That runs jobs on the runner, can access another user’s code that runs on the

With shared runners, this means that anyone

#Git submodule set branch 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 project 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. Automatically rotate authentication tokens Configuring runners.View statistics for runner performance.Determine which runners need to be upgraded.Configure fastzip to improve performance.System calls not available on shared runners.Sync or exclude specific submodules from CI jobs.Configure runner behavior with variables.Use tags to run jobs on different platforms.Use tags to control which jobs a runner can run.Determine the IP address of a project runner.Determine the IP address of a shared runner.Reset the runner registration token for a project.Prevent runners from revealing sensitive information.