admin管理员组文章数量:1391969
I'm currently trying to run multiple pipelines on multiple runners using concurrent execution in GitLab CI.
The problem is: some of the jobs are very resource consuming, some are not. I want to run only one resource-consuming job on a single runner, leaving the rest of runner concurrency for the rest of jobs.
I heard about resource groups, but it is not exactly resolves the problem - high-loading jobs still have to run in parallel, but on different runners. (In other words we want to avoid the situation when two resource-consuming jobs being run on the same runner)
Is it possible to do that somehow?
I'm currently trying to run multiple pipelines on multiple runners using concurrent execution in GitLab CI.
The problem is: some of the jobs are very resource consuming, some are not. I want to run only one resource-consuming job on a single runner, leaving the rest of runner concurrency for the rest of jobs.
I heard about resource groups, but it is not exactly resolves the problem - high-loading jobs still have to run in parallel, but on different runners. (In other words we want to avoid the situation when two resource-consuming jobs being run on the same runner)
Is it possible to do that somehow?
Share Improve this question edited Mar 13 at 14:33 DummyThatMatters asked Mar 13 at 12:01 DummyThatMattersDummyThatMatters 293 bronze badges1 Answer
Reset to default 0I was able to solve the problem by creating two runners per machine - one with high-load
tag and another with normal tag. For high-load runner I've used limit=1
flag to prevent it from taking more than one job simultaneously. And of course you have to mark every resource-consuming job with high-load
tag in order to make thing work.
本文标签:
版权声明:本文标题:continuous integration - How to limit the number of concurrent execution of high-loading jobs for a GitLab runner? - Stack Overf 内容由网友自发贡献,该文观点仅代表作者本人, 转载请联系作者并注明出处:http://www.betaflare.com/web/1744702274a2620629.html, 本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌抄袭侵权/违法违规的内容,一经查实,本站将立刻删除。
发表评论