logicsoli.blogg.se - Gitlab branching strategy

#Gitlab branching strategy registration

Of shared runners on large GitLab instances. To avoid exposing sensitive information, you can restrict the usage The job, if running longer, times out after 30 minutes Protecting 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 runner authentication tokens Configuring runners.

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.

#Gitlab branching strategy registration

Reset the runner registration token for a project (deprecated).Using shared runners in forked projects.Prevent runners from revealing sensitive information.