5 ms·
if I remember correctly CircleCI is the only CI-provider that would let you run their pipelines/actions locally in a Docker container. That worked really well f
by vnglst 6y ago
if I remember correctly CircleCI is the only CI-provider that would let you run their pipelines/actions locally in a Docker container. That worked really well for me, quick feedback loop without creating commits.
- cbb330 6y agoGitlab also offers this feature [0] [1] [0] - https://docs.gitlab.com/ee/ci/quick_start/#ensure-you-have-runners-available https://docs.gitlab.com/ee/ci/quick_start/#ensure-you-have-r... [1] - https://medium.com/@umutuluer/how-to-test-gitlab-ci-locally-f9e6cef4f054 https://medium.com/@umutuluer/how-to-test-gitlab-ci-locally-...
- mdaniel 6y agoI've resorted to running my own local copy of GL (and, of course, its runner) for troubleshooting build complexity, since their runner pool has been so indescribably bad of late: https://status.gitlab.com/pages/history/5b36dc6502d06804c08349f7/component/5b36e06c633e9004b3d624ad https://status.gitlab.com/pages/history/5b36dc6502d06804c083... I agree with the other comments that CircleCI is my high-bar for "how can a sane person run the build locally?" because I also agree with the other comments that "act" is handy, but only for the most trivial of hello-world builds, and `gitlab-runner exec` is a cruel joke
- mfontani 6y agoDrone CI, too - you can "drone exec" a pipeline and it'll work the same way as on the CI server. It's a great feature to have.
- awwaiid 6y agoCodeship does this too with their `jet` command.