If you don't want to self-host Gitea/Forgejo, I recommend SourceHut for private repos and Codeberg for public ones. Happy to answer any questions you might have for either based on my experience!
Incident with Actions and Pages
91–100 of 407 posts
Re: Incident with Actions and Pages
#92Earlier quoted context omitted.
Founder of Depot here. To my knowledge, we are the first engine to support different syntaxes in this compatible way via Depot CI [0]. Great time to try it out and let us know your thoughts! We’ve built a lot of cool stuff into it like parallel steps, custom images, and a full CLI/API interface so you can literally everything without going into the web app. [0] https://depot.dev
Are you able to bring your own runners? Our org is heavily invested in self-hosted runners at this point and have gotten a pretty tremendous value from it. I think we'd be wise to get away from GitHub's control plane but keep running jobs in our own infra.
[deleted]
Re: Incident with Actions and Pages
#93If you don't want to self-host Gitea/Forgejo, I recommend SourceHut for private repos and Codeberg for public ones. Happy to answer any questions you might have for either based on my experience!
Re: Incident with Actions and Pages
#94Are there any GitHub Actions-compatible CI services out there that don't rely on their infrastructure? I know of depot's but no others; are these resilient to these outages or do they still lose functionality? I imagine the latter but I don't know.
there are a couple and have very good reputation - though I've never used them https://www.blacksmith.sh/ and https://runs-on.com/ They also say that they're much cheaper than github
I think both of these provide nodes that are scheduled using GitHub's control plane. They would also not be working right now.
Re: Incident with Actions and Pages
#95Does anyone use any good alternatives to GitHub Actions?
Re: Incident with Actions and Pages
#96[deleted]
Re: Incident with Actions and Pages
#97And it is bypassing mandatory GHA Pipeline check and giving green. So be careful when merging/reviewing your PRs cause.
Re: Incident with Actions and Pages
#98Re: Incident with Actions and Pages
#99I moved a while back to Forgejo -> https://forgejo.org couldn't be happier. Highly recommended.
Re: Incident with Actions and Pages
#100I've started spending each github outage planning our move to an alternative. I guess I'm not alone. Where are you all moving?
We use TeamCity for CI builds, before that Jenkins. Only accessible from the inside of the network.
Even though it's selfhosted and we don't have a dedicated infrastructure team, I don't remember it ever being down in the last 12 years I have been working here.