3 ms·
"If you runners overload your CI system now both go down" Isn't that a bit worrisome?
by transfire 11y ago
"If you runners overload your CI system now both go down" Isn't that a bit worrisome?
- jobvandervoort 11y agoWhere does it say that? It should say that they don't both go down! Runners are fully external to GitLab and GitLab CI. This means they will never interfere with GitLab's functioning. You should not host a Runner on a GitLab instance. It was not intended like that and in the documentation we explicitly tell you to not do this.
- transfire 11y agoI feel much better about it now. Thanks. I read it under "advantages and disadvantages".
- haynes 11y agoAhh I know where that came from. The runners push the build results back to the coordinator (which is now included in gitlab). So in theory, if you have a large number of runners and a very large number of concurrent builds, it could slow down gitlab a little bit. But the numbers you need to reach this are pretty high.