Isn't one of the main selling points of Gitlab their built-in CI? Anyone using Gitlab use an external CI?
Or, I guess a more conciliatory stance is: wow, folks must be using some pretty hello-world pipelines if `gitlab-runner exec` works for you
31–40 of 124 posts
Isn't one of the main selling points of Gitlab their built-in CI? Anyone using Gitlab use an external CI?
Or, I guess a more conciliatory stance is: wow, folks must be using some pretty hello-world pipelines if `gitlab-runner exec` works for you
How can a CI-service not support ANY GIT source? All this garbage surrounding GIT is just baffling.
Made worse by: ok, fine, you magically have `eval $(git set-env-from-commit HEAD)`, now how do you report those run results back to the upstream UI, since there is for sure no standard for that
Who even uses external CIs anymore? GitHub and gitlab ones are great otherwise you have plenty you can deploy yourself.
Isn't one of the main selling points of Gitlab their built-in CI? Anyone using Gitlab use an external CI?
Who even uses external CIs anymore? GitHub and gitlab ones are great otherwise you have plenty you can deploy yourself.
Isn't one of the main selling points of Gitlab their built-in CI? Anyone using Gitlab use an external CI?
As a long-time GitLab CI user, I do miss how the local circleci runner binary just worked . I am aware of gitlab-runner but it is a sick joke designed to mislead folks who just skim the docs into believing that they have a local execution story Or, I guess a more conciliatory stance is: wow, folks must be using some pretty hello-world pipelines if `gitlab-runner exec` works for you
Still no support for arm64 docker executors after years of asking for it.
https://circleci.com/docs/using-arm
I know it's not as convenient as being able to use a docker executor directly, but it seems straightforward to work around.
Earlier quoted context omitted.
What does it mean to be more philosophically aligned with one corporation vs another?
That the buyer believes in the same thing the company "believes" in. Eg: GitLab has an open-core product and GitHub is owned by (evil?) Microsoft.
Earlier quoted context omitted.
It appeals to me as someone who likes Circle's CI offering but wants to move away from Github. I tried using Gitlab's CI and was surprised at how limited it was. The Gitlab CI syntax was harder to follow, and my integration tests took 17m to run when they ran in almost 1/3 the time on Circle. A big part of the problem was that CircleCI lets me use an instance with 8 CPUs / 16 GB RAM with just a config file change[0],…
Related, GitHub has had 'use more powerful hosted runners' in the pipeline for over 2 years[0]. This issue replaced another now-deleted issue[1] from July 2020. Really disappointing, as I've had to resort to using `az vm start` -> run -> `az vm deallocate` to use an on-demand powerful runner. 0: https://github.com/github/roadmap/issues/161 1: https://github.com/github/roadmap/issues/95 (note: added `ga` `ae` and remo…