I literally set up some GitHub actions today for the first time in my life, I was really pumped about getting into the CI/CD game with my latest open repository. A couple of hours ago everything was going great, running a workflow needed maybe 40 seconds max. Now, they are not running at all. That all happened while I was thinkering with the yaml workflow file, so the disruption of the service made me believe that it was me who broke something :P it's been a nice first experience with CI/CD though, never going back to building my self.
Check my GitHub repo (see my bio) to see it's true haha
Think of the poor grandma yesterday who was finally convinced to get a Facebook account to see the grandkids and right as she hits "create account" Facebook goes down worldwide.
No force on earth will convince her she didn't do it.
But seriously, what's going on with all the service disruptions? From slack to all of facebook to GitHub (who had 7 incidents in September). Maybe centralizing the whole internet into a few providers isn't a good idea after all?
> Maybe centralizing the whole internet into a few providers isn't a good idea after all?
Everything's tradeoffs, economies of scale for centralising- easy to blame the provider if a fuckup happens.
But when it goes down it stops everything; same issue with AWS, Azure's ADFS, Cloudflare, ad infinitum. Half the internet can go away at a moments notice or the provider can turn on you personally because an automated bot dislikes your username and decides to blacklist your company.
(is my bias showing?)
Anyway, Late September/Early October is rife with outages for as long as we've been running internet services.
People speculate that it's the influx of new sysadmins/programmers, but that's debated.
Running services at scale is hard! And having everything in the cloud does put all of your eggs in a single basket. Also having all on-prem, home-built stuff is the same problem (eg. Facebook). Hybrid cloud solutions should help somewhat with impact when a service provider goes down, hopefully you can shunt your services locally and isolate yourself from the problem. But I doubt anyone is really doing that at scale either.
[+] [-] RapperWhoMadeIt|4 years ago|reply
[+] [-] bombcar|4 years ago|reply
No force on earth will convince her she didn't do it.
[+] [-] danuker|4 years ago|reply
If your test suite takes 40 seconds, is it not quicker and easier to run locally than the overhead of another git commit to get feedback?
[+] [-] hivacruz|4 years ago|reply
By the way, just discovered a nice library to test GitHub Actions locally: https://github.com/nektos/act
[+] [-] stuff4ben|4 years ago|reply
[+] [-] vexcaustic|4 years ago|reply
But seriously, what's going on with all the service disruptions? From slack to all of facebook to GitHub (who had 7 incidents in September). Maybe centralizing the whole internet into a few providers isn't a good idea after all?
[+] [-] dijit|4 years ago|reply
Everything's tradeoffs, economies of scale for centralising- easy to blame the provider if a fuckup happens.
But when it goes down it stops everything; same issue with AWS, Azure's ADFS, Cloudflare, ad infinitum. Half the internet can go away at a moments notice or the provider can turn on you personally because an automated bot dislikes your username and decides to blacklist your company.
(is my bias showing?)
Anyway, Late September/Early October is rife with outages for as long as we've been running internet services.
People speculate that it's the influx of new sysadmins/programmers, but that's debated.
[+] [-] stuff4ben|4 years ago|reply
[+] [-] simzor|4 years ago|reply
[+] [-] unknown|4 years ago|reply
[deleted]
[+] [-] the-dude|4 years ago|reply
Anyways, Twitter will be down next week. You've read it here first.
[+] [-] manojlds|4 years ago|reply
[+] [-] paulvnickerson|4 years ago|reply
[+] [-] jvolkman|4 years ago|reply
[+] [-] matsemann|4 years ago|reply
[+] [-] thinkafterbef|4 years ago|reply
Our whole business[1] relies on GitHub Actions functioning. It just sucks.
[1] https://buildjet.com/for-github-actions
[+] [-] justusthane|4 years ago|reply
Github Action 2vCpu / 8 GB RAM
BuildJet Runner 4 vCpu / 16 GB RAM
Also, should probably be capitalized as "vCPU".
[+] [-] weird-eye-issue|4 years ago|reply
[+] [-] k4runa|4 years ago|reply
[+] [-] mrits|4 years ago|reply
[+] [-] xmpirate|4 years ago|reply
[+] [-] corobo|4 years ago|reply
[+] [-] mcintyre1994|4 years ago|reply
[+] [-] mpolichette|4 years ago|reply
[+] [-] sergiotapia|4 years ago|reply
[+] [-] hirako2000|4 years ago|reply
[+] [-] roemerb|4 years ago|reply