News for hackers. Stuff that matters.

A comment on Show HN: Test your Gitlab CI Pipelines changes locally using Docker.

Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by Nullabillity on Wednesday February 24, 2021 @05:10AM (#26248432)
Why not just use GitLab's runner[0] directly for this?

    gitlab-runner exec docker <job>
[0]: https://docs.gitlab.com/runner/install/
[ Parent | on HN ]
Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by damnhotuser on Wednesday February 24, 2021 @05:26AM (#26248516)
Yeah 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.
[ Parent | on HN ]
Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by vergessenmir on Wednesday February 24, 2021 @06:41AM (#26248925)
Haven'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?

[ Parent | on HN ]
Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by jayd16 on Wednesday February 24, 2021 @11:52AM (#26252160)
Sure 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/

[ Parent | on HN ]
Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by sjburt on Wednesday February 24, 2021 @12:37PM (#26252885)
When using the "exec" command it doesn't do that. It just executes one job, not the whole pipeline.
[ Parent | on HN ]
Re:Show HN: Test your Gitlab CI Pipelines changes locally us... by carlosf on Wednesday February 24, 2021 @08:19AM (#26249517)
exec is extremely limited and it's not being actively maintained.
[ Parent | on HN ]