The concurrent parameter does not limit the number of VMs.Īs detailed here, one process can be configured to manage multiple runner workers. To limit the number of virtual machines (VMs) created by the Docker Machine executor, use the limit parameter in the ] section of the config.toml file. Limit the number of VMs created by the Docker Machine executor If the job is not assigned to the runner, then the lock on the idle VM is released and the VM is returned back to the pool.If the job is assigned to the runner, then that job is sent to the previously acquired VM.The runner acquires an existing idle VM before asking for a new job. If the IdleCount is set to a value greater than 0, then idle VMs are created in the background. The IdleTime period, the machine is removed. The machine is waiting for the next jobs, and if no one is executed, after After the job is finished, the autoscaling Machines are always created on-demand before each job (if there is noĪvailable machine in Idle state). There is also a special mode, when you set IdleCount = 0. In GitLab Runner - Advanced Configuration - The section Additional configuration information In GitLab Runner - Advanced Configuration - The section. For autoscale, it’s the upper limit of machines created by this provider (in conjunction with concurrent and IdleCount).Ĭonfiguration parameters details can be found Limits how many jobs can be handled concurrently by this specific token. To use the autoscale feature, executor must be set to docker+machine. Together with limit (from ] section) and IdleCount (from section) it affects the upper limit of created machines. This is the most upper limit of number of jobs using all defined runners, local and autoscale. Limits how many jobs globally can be run concurrently. This section describes the significant autoscale parameters. The autoscale mechanism is based on Docker Machine.Īll supported virtualization and cloud provider parameters are available at the Optionally use a forked version of Docker machine supplied by GitLab, which has some additional fixes.On for the GitLab Community Edition project:Įach machine on the chart is an independent cloud instance, running jobs In case of many cloud providers this helps to utilize the cost of already usedīelow, you can see a real life example of the GitLab Runner autoscale feature, tested Wait to run the next jobs or can be removed after the configured IdleTime. Those machines, after the job is finished, can When this feature is enabled and configured properly, jobs are executed on Strategy in response to the deprecation of Docker Machine Runners on public cloud virtual machines. Docker has deprecated Docker Machine, the underlying technology used to autoscale
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |