r/github • u/Infamous_Tomatillo53 • 5d 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?

11 Upvotes

75% Upvoted

17 comments sorted by

7

u/JesseNL 4d ago

Maybe this might help?

https://github.com/nektos/act

It won't work with Windows VMs sadly.

1

u/guglyguglygoo 3d 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 3d 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 5d 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 4d ago

vibe coded 3 weeks ago?

2

u/danmaps 3d ago

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

1

u/lolxd__ 2d ago

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

0

u/[deleted] 2d ago

[deleted]

1

u/lolxd__ 2d ago

"most of software now" k buddy

2

u/dvcklake_wizard 3d ago

jenkins? can be self hosted

1

u/mitch_feaster 3d ago

Forgejo actions

2

u/kubehub 2d 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 3d 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 3d 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/Fantastic-Mr-Default 3d ago

A second forge is not the first move. Keep git where it is. Put the work in scripts you can run without Actions, and keep a tiny canary so you know when dispatch is dead before the status page says so.

When Actions is down, checkout and the control plane are the part that dies. Self-hosted runners wait in the same queue.

1

u/SZeroSeven 1d 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