3 ms·
Not my experience at all, in a similarly sized premium on-prem GitLab. I git-push and the pipeline is running faster than I can get to my browser. Jobs queue ba
by jamesmontalvo3 4y ago
Not my experience at all, in a similarly sized premium on-prem GitLab. I git-push and the pipeline is running faster than I can get to my browser. Jobs queue basically instantly assuming you have enough runners for your workloads.
I have no experience with using the search. On both GL and GH I prefer to just pull the code and search with my preferred local tools.
Personally I find GitLab CI syntax better to work with than GitHub, particularly if using dependency-based versus using stage-based workflow.
- deng 4y agoWell, they have an epic for improving pipeline creation, so it's not just me: https://gitlab.com/groups/gitlab-org/-/epics/7290 https://gitlab.com/groups/gitlab-org/-/epics/7290 The reason it is so slow for us is probably because we use a lot of external includes and trigger jobs. But as I said: the problems start once you scale things up. Then you also cannot just "pull the code" for a search, as we also have a lot of repositories.