Conversation
jarkko

Jarkko Sakkinen

Edited 3 months ago
I've been looking this tool for years and it was there all the time: https://github.com/firecow/gitlab-ci-local

My workflow has been before:

1. Edit .gitlab-ci.yml without knowing what I'm actually doing.
2. git push
3. Hope for the best, fear for the worst.

It has been pretty difficult to learn it when I have to test every edit remotely and once I reach my quota wait for some weeks to continue.

And no, GitLab runner is not a solution:

1. I've never been able to successfully set it up.
2. It does not scale to multiple Gitlab instances easily.
3. Even if two former were somehow addressed I do not want to run random system daemons.

I.e. to summarize: A local Gitlab runner sucks. It sucks unimaginably hard.

#gitlab #ci
1
0
2
dwagenk@chaos.social

dwagenk

Reply to @jarkko

@jarkko yes, can confirm it is a great tool to use. Especially if you don't like pushing "let's try if this works" commits over and over to get the ci config file correct.

It's not always 100% identical to gitlab CI in how it runs the jobs, so if something behaves strange test if the behavior on your gitlab instances CI server is the same before going down the debugging rabbit-hole...

1
0
1
jarkko

Jarkko Sakkinen

Reply to @dwagenk@chaos.social
@dwagenk Yep, exactly. It is definitely still better than my previous approach ;-)
0
0
1
About social.kernel.org

Terms of service

  1. Please do not use this service in violation of the Linux Kernel Code of Conduct. Doing so will result in your account suspension with the referral of the matter to the CoC committee.

  2. "Repeating"/"boosting" someone else's status on this platform will be treated as endorsement and will fall under rule #1.

  3. You are encouraged to use this platform to promote your work on the Linux Kernel, but there is no restriction on permitted topics (with the exception of anything covered by #1 above).

  4. There is no requirement to post in English, but it should be considered the primary language of communication on this platform.

Privacy notice

The admins of this service have access to all posted statuses. They aren't looking, but if it's something they shouldn't know about, then you should not post it on this platform.

Please see the Linux Foundation Privacy Policy, which applies to this platform as well.

Getting your own account

If you would like an account on this instance, please check that the following applies to you:

  • You are listed in MAINTAINERS or CREDITS

  • OR: You have a kernel.org account or email address

  • OR: You have a long and established history of involvement with the Linux Kernel

If the above is true and you agree with the Terms of Service and Privacy Notice listed above, please use these instructions to request an account: