In most of the scenarios, if GitHub Actions is down for an hour, even a couple of times per year, the deployment of new functionalities may be delayed a bit but that's it.
If you average over the year, the productivity gain, simplicity, and price (100% free for public repos!) from using GitHub Actions is still worth it for most of the people.
There could have been many uncontrollable reasons for the flow of developers to be interrupted (meeting, lunch, questions from colleagues, a pet in the office, slow internet, traffic with the car, stuck in an elevator) or just big news-related distractions (Christmas, Gamestop stock, Roblox IPO).
Unless you have a company somewhat relying on GitHub Actions for critical / business-generating flow (this sounds like an unusual idea to me but ok), it's unlikely to impact the income of the company.
We're all in on Github actions these days but there was a time when we used to maintain our own Jenkins instance. I have spent less time waiting for the occasional Github problem to be resolved than I did trying to keep that thing working.
Unless you're building custom actions for your workflows I think you should be fine.
Generally on all the projects were I have setup GitHub actions it just installs system/project packages and executes shell commands/scripts.
So if it's down, as a developer I can just run the same commands locally.
Sure, there are a few GitHub specific things in there, but mostly for developet experience. E.g. commenting back on PR, inline CI error messages, uploading release tarballs automatically.
I wouldn't call it prudent to go all-in on any cloud service, whether it's Github (both for VCS and CI/CD), AWS, or moving your entire office suite onto Google Workspace.
You should be able to run your test suite and deploy locally, CI is all about automating the process and utilising remote resources rather than your bogging down your dev machine.
It depends.
In most of the scenarios, if GitHub Actions is down for an hour, even a couple of times per year, the deployment of new functionalities may be delayed a bit but that's it.
If you average over the year, the productivity gain, simplicity, and price (100% free for public repos!) from using GitHub Actions is still worth it for most of the people.
There could have been many uncontrollable reasons for the flow of developers to be interrupted (meeting, lunch, questions from colleagues, a pet in the office, slow internet, traffic with the car, stuck in an elevator) or just big news-related distractions (Christmas, Gamestop stock, Roblox IPO).
Unless you have a company somewhat relying on GitHub Actions for critical / business-generating flow (this sounds like an unusual idea to me but ok), it's unlikely to impact the income of the company.
We're all in on Github actions these days but there was a time when we used to maintain our own Jenkins instance. I have spent less time waiting for the occasional Github problem to be resolved than I did trying to keep that thing working.
I agree with Jenkins, but, Gitlab-CI is a joy to work with.
Honest question, but isn't the backup plan just to run your CI/CD locally?
Github actions being down so far as only affected me once before and now today. However, like before I just ran the tests/deploy locally.
I've always thought of CI/CD as just a way for me to be lazy only requiring me to push a commit and move on with my day
Unless you're building custom actions for your workflows I think you should be fine.
Generally on all the projects were I have setup GitHub actions it just installs system/project packages and executes shell commands/scripts.
So if it's down, as a developer I can just run the same commands locally.
Sure, there are a few GitHub specific things in there, but mostly for developet experience. E.g. commenting back on PR, inline CI error messages, uploading release tarballs automatically.
I wouldn't call it prudent to go all-in on any cloud service, whether it's Github (both for VCS and CI/CD), AWS, or moving your entire office suite onto Google Workspace.
You should be able to run your test suite and deploy locally, CI is all about automating the process and utilising remote resources rather than your bogging down your dev machine.
rvz_told_you_so_linked_list
You sir are a legend.