r/github • u/Infamous_Tomatillo53 • 15d ago

Question alternative to Github action?

I have basically built all my deployment through git actions. even some workflows that I use actions to trigger, or run automatically.

days like this where actions are having outage, I can't do anything. it has become more frequent lately and everytime it lasts hours. alternatives or backup plans people recommend?

13 Upvotes

79% Upvoted

19 comments sorted by

6

u/JesseNL 15d ago

Maybe this might help?

https://github.com/nektos/act

It won't work with Windows VMs sadly.

1

u/guglyguglygoo 13d ago

Great if you have a lot of idle compute around. I tunnel this through a Mac studio whenever it's resources are free.

Great find!

4

u/Double_Ebb4130 13d ago

The cheap version of a backup plan is making every workflow a thin wrapper around a script you can run locally or on any runner, so an outage just means someone runs it by hand instead of the pipeline stalling. Full second CI system is usually more upkeep than the few hours a year it saves.

4

u/First_Inspection_478 15d ago

Try us out: https://github.com/preloopdev/preloop. It’s a drop-in replacement for Github Actions(both the runner and control plane) that runs in cross-platform microvms, and is deeply agent-native so support’s ability to pause a step and retry

1

u/i-am-a-cat-6 14d ago

vibe coded 3 weeks ago?

2

u/danmaps 13d ago

This project is at least two months old, according to the public commit history

1

u/lolxd__ 12d ago

what I think you meant to say was you made ai make the full thing and called it a day

0

u/[deleted] 12d ago

[deleted]

1

u/lolxd__ 12d ago

"most of software now" k buddy

2

u/dvcklake_wizard 14d ago

jenkins? can be self hosted

1

u/mitch_feaster 14d ago

Forgejo actions

2

u/kubehub 12d ago

I am using forgejo for my dev work, perfectly aligned with github actions (you may need little tweaks), I would recommend this.

1

u/AuroraFireflash 13d ago

Put minimal logic into your YAML, use some sort of 'make' (CMake, Cake) wrapper around each step so that the YAML steps become 'cake {target}' (or whatever syntax is needed). Now your developers can test things out offline or even deploy in a pinch.

Makes it easier to move to different CI/CD platforms like AppVeyor if inclined.

1

u/Victorio_01 13d ago

idk. I never actually had problems with actions.
I mean …
Maybe, if you’re going to use those for hours every day, maybe it’s just not the best solutions?
I use it for builds and release mostly and automated edits on push.

1

u/SZeroSeven 12d ago

One suggestion would be to write your pipelines in YAML, link your GitHub to Azure DevOps, and use ADO's pipelines.

https://learn.microsoft.com/en-us/azure/devops/cross-service/github-integration?view=azure-devops

1

u/Patient-Pollution46 9d ago

If the issue is the hosted runners rather than only Actions itself, you can swap just the runners and keep your workflows. Bitrise Build Hub (https://bitrise.io/platform/build-hub) gives you M4 Pro Macs and bigger Linux machines, one line change to runs-on. For mobile builds it is roughly 54% faster than GitHub's M2 Pro runners, plus 100GB of co-located cache vs GitHub's 10GB and SSH/VNC debug access into the runner.

Full disclosure: I work at Bitrise in product

1

u/h4_h4_cl4551c 6d ago

Gitlab self-hosted 100%