31–40 of 89 posts
Still having regular incidents at GitHub in 2024, even with Microsoft's infrastructure after 5 years since the acquisition with something always going down. Just expect GitHub to go down at least once every month as it is that unreliable. This certainly has aged well: [0] [0] https://news.ycombinator.com/item?id=22868406
And just as we're about to migrate 4 kubernetes clusters with a total of ~4k pods. Terraform in github actions on selfhosted runners and argoCD is failing.
That's where I feel like it's actually pretty nice to not have CI tied to your source code. It's probably more expensive to use Travis/Circle but at least you don't have a single point of failure for deploys.
In the old days we had mirrors for many online repositories.
We just hope SMTP keeps ticking along somehow or we're fcuked.
In the old days we had mirrors for many online repositories.
Earlier quoted context omitted.
That's where I feel like it's actually pretty nice to not have CI tied to your source code. It's probably more expensive to use Travis/Circle but at least you don't have a single point of failure for deploys.
Doesn't this give you 2xSPF? Or can I use my local copy of the source to kick of Travis/Circle?
You should always engineer things so you can fall back to something akin to:
./scripts/deploy_the_things
Ideally backed by a real build system and task engine ala Bazel, Gradle, whatever else floats your boat.
It also means you are free to move between different runners/CI providers and just have to work out how to re-plumb secrets/whatever.
GH actions/friends really provide minimal value, the fact they have convinced everyone that encoding task graphs into franken-YAML-bash is somehow good is one of the more egregious lies sold to the development community at large.
The fact that Github has been so unstable for so long is absolutely insane to me. I know ops is hard, but this level of consistent outage points to an endemic problem. Is it the legacy rails/mysql stack that is the largest culprit or is there systemic rot in the engineering org?
The fact that Github has been so unstable for so long is absolutely insane to me. I know ops is hard, but this level of consistent outage points to an endemic problem. Is it the legacy rails/mysql stack that is the largest culprit or is there systemic rot in the engineering org?
Has it?
I’ve had hardly any problems. Occasional issues, but rarely have I been impacted to the extent I notice for more than say an hour…. maybe I notice it a couple times a year.
My internet access at home is more likely the issue when I hit GitHub issues.
Earlier quoted context omitted.
Why people think it can be related to Rails when there are tons of companies out there using Rails not affected by this degradation?
One difference is that Rails and MySQL on a Github scale is rare, even when taking into account Github scale is rare.
Earlier quoted context omitted.
That's where I feel like it's actually pretty nice to not have CI tied to your source code. It's probably more expensive to use Travis/Circle but at least you don't have a single point of failure for deploys.
Doesn't this give you 2xSPF? Or can I use my local copy of the source to kick of Travis/Circle?