Programming

19703 readers

279 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 2 years ago

MODERATORS

[email protected]

Any suggestions for a self-hosted CI that can also be run locally? (programming.dev)

submitted 1 week ago by [email protected] to c/[email protected]

36 comments fedilink hide all child comments

I left Github a while ago and have been relying on simple pre-push scripts in my workflow, but would like to be able to test PRs from others without putting my machine at risk. Besides codeberg and radicle (neither of which have reliable CI), I also have a build machine, where I could run CI jobs, however it is important that the CI jobs can also run locally so that external people do not require access to the build machine.

Is there a CI that can do those things (run locally and remotely)?

Anti Commercial-AI license

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 0 points 1 week ago (1 children)

would like to be able to test PRs from others without putting my machine at risk

I know what you mean, but do you not read the diff? Are you working on codebases that are so obfuscated that you can't spot a malicious command?

[–] [email protected] 1 points 1 week ago* (last edited 1 week ago) (1 children)

What if they pull in a new dependency with a CVE or that executes malicious code? How am I supposed to check that? Or what if I miss a bug in the justfile or shell script?

Anti Commercial-AI license

[–] [email protected] 2 points 1 week ago (1 children)

Run your CI in a sandbox.
For example gitlab allows you to run in a docker image.
Unless the attacker knows a docker CVE or is willing to waste a specter style 0-day on you, the most they can do is waste your cpu cycles.

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago)

Yep. Hell, be very paranoid and run it in a container on a runner VM on your box if you like.

And you can use podman or sysbox there.