Live data from Hacker News

Show HN: Test your Gitlab CI Pipelines changes locally using Docker

github.com

1–10 of 41 posts

Re: Show HN: Test your Gitlab CI Pipelines changes locally using Docker

#3
post #2

Interesting repo! It would be great to have more documentation since I am a beginner in Docker.

Not personal, maybe your unfamiliarity with Docker means you're not the target audience. I mean getting people up to speed with Docker is a bit of an ocean to boil, and this project appears to be small of resources...

Re: Show HN: Test your Gitlab CI Pipelines changes locally using Docker

#7

Why not just use GitLab's runner[0] directly for this? gitlab-runner exec docker [0]: https://docs.gitlab.com/runner/install/

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.

Re: Show HN: Test your Gitlab CI Pipelines changes locally using Docker

#8
post #5

This looks interesting. Will test it out. Hope it works with includes.

Yeah it does work with includes. One of the pain point right now is that it does not work with cache:untracked or artifacts:untracked, but I'm trying to figure it out :)

Re: Show HN: Test your Gitlab CI Pipelines changes locally using Docker

#10

Great idea. One question - what pain point is this solving? As a GitLab, GitLab Pipeline and Docker user I don't find running pipelines that slow to run or initiate

Personally with Github Actions, I do find myself pushing 2, 3 or 4 times just getting the pipeline working because I always mess something up, either I've messed up a command or the environment isn't what I expected etc. There's act[0] for github which I should use more often to solve this, but I usually forget

[0]: https://github.com/nektos/act

Post reply on HN