this post was submitted on 22 May 2026
297 points (97.4% liked)
Technology
84866 readers
3979 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't know how Woodpecker works, but I have a lot of experience with Gitlab runners. You can startup a runner locally, as it doesn't need to be publicly accessible from the internet. Only the Gitlab instance needs to be accessible for the runner, as the runner actively fetches new jobs from there and pushes the results again.
If Woodpecker works similarly, you could just deploy the runner locally while you're actively developing and your computer is running anyway, if you don't want to pay for a VPS.
That's how it works that I can see. I run it and woodpecker just waits for an event like a push or whatever to your repo and then it runs the jobs.
As someone who runs gitlab as well I much prefer woodpecker CI to github/forgejo actions. Personal preference entirely though.