4 ms·
Why not just use GitLab's runner[0] directly for this? gitlab-runner exec docker <job> [0]: https://docs.gitlab.com/runner/install/ https://docs.gitlab.co
by Nullabillity 6y ago
Why not just use GitLab's runner[0] directly for this?
gitlab-runner exec docker <job>
[0]: https://docs.gitlab.com/runner/install/ https://docs.gitlab.com/runner/install/
- damnhotuser 6y agoYeah I thought about that, but gitlab-runner doesn't allow to "share" cache or artifacts between jobs so it's not a good fit to test multiple-jobs workflows.
- vergessenmir 6y agoHaven't test the tool yet. Neither do I know how close the behaviour of the pipeline locally will differ on the server. Saying that, pipeline test tools are very much needed. Making commits and refreshing a UI is not practical. I can test a distributed pipeline on spark why can't I do that with modern CI/CD?
- jayd16 6y agoSure it does. Jobs have a shared cache (although this can be slow) and artifacts are shared to downstream jobs. Maybe this is a tiered feature? https://docs.gitlab.com/ee/ci/caching/ https://docs.gitlab.com/ee/ci/caching/
- sjburt 6y agoWhen using the "exec" command it doesn't do that. It just executes one job, not the whole pipeline.
- carlosf 6y agoexec is extremely limited and it's not being actively maintained.