Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Incident with GitHub Actions

githubstatus.com

Post reply on HN
Print view View original

21–30 of 50 posts

Re: Incident with GitHub Actions

#21

Post by Shadonototra »

phoe-krk wrote: post #3

Previous GitHub incidents in March 2022: * on 16th, https://www.githubstatus.com/incidents/fpk08rxnqjz2 * on 17th, https://www.githubstatus.com/incidents/sksd097hm0y5 * on 22nd, https://www.githubstatus.com/incidents/83lq7ftk19r5 * on 23rd, https://www.githubstatus.com/incidents/tyc8wpsgr2r8 * on 24th, https://www.githubstatus.com/incidents/y5hdmv0p49x3

scaling is a hard problem to solve, so props to them for doing it without too much issues, overall..

but damn, since the microsoft acquisition, they are having more issues more frequently

Re: Incident with GitHub Actions

#22

Post by ho_schi »

somehnacct3757 wrote: post #16

As the person who gets pinged when our CI isn't working, I'm hoping my next employer doesn't have github in their stack. We've reached the stage where architectural decisions are being questioned. Nobody should need to ask me "well why are we using github?" but here we are. They needed to fix this two weeks ago. The next time I'm in charge of stack decisions I will be evaluating competitors. This is exactly how Slack…

Host on premise? Or use Gitlab as service or - again - on premise. Outsourcing in general and literally "outsourcing" should be done for things you cannot do yourself properly (no competence, too much work, no feasible resources).

Long read but describing it neatly: https://danluu.com/nothing-works/

A decision between - do you pay your personnel for doing it - or - do you give others money and hope they do it in a way which is good enough. Outsourcing as trend failed because it was driven by capitalism isn't a new finding. And as convenient removte web services are, the cloud is outsourcing.

Re: Incident with GitHub Actions

#23

Post by akmittal »

RapperWhoMadeIt wrote: post #11

I would maybe start migrating repos away from GitHub, since they have proven to be quite unreliable. Nonetheless, I must say I do appreciate GitHub's UI and even their CLI is quite nice. Is there a service out there that basically provides the same good user experience, CI/CD and has no costs for public repos? Apart from the unreliability I can't complain about GitHub.

https://Gitlab.com seem to be pretty good

Re: Incident with GitHub Actions

#24

Post by rvz »

hypeatei wrote: post #12

I think it's easy to pile-on and say "GitHub is down again! Should've self hosted lol!". When, in reality, it's one service having issues and not the whole site. These incidents also seem to be resolved quickly. Downtime is not the end of the world.

Judging from last month [0] and my own comment chain, [1] it is not so good and it is like as if it is guaranteed to go down each month.

> Downtime is not the end of the world.

What if you needed to push that critical change and it is down and all you could do is wait?

What if you hosted your website on GitHub Pages? Maybe you use GitHub Actions (I assume most do here and are paying for it for their teams). Surely people use it for pull requests and issue management as well as for the webhooks and basic git operations.

There are those that went 'all in' on GitHub and use everything on it and are now crying that it is unreliable. This is where going 'all in' makes no sense. (Especially without a backup/self-hosted system somewhere.) Or centralizing everything on it as predicted years ago. [2]

[0] https://news.ycombinator.com/item?id=30841070

[1] https://news.ycombinator.com/item?id=30790842

[2] https://news.ycombinator.com/item?id=22867803

Re: Incident with GitHub Actions

#25

Post by rurban »

Shadonototra wrote: post #21
phoe-krk wrote: post #3

Previous GitHub incidents in March 2022: * on 16th, https://www.githubstatus.com/incidents/fpk08rxnqjz2 * on 17th, https://www.githubstatus.com/incidents/sksd097hm0y5 * on 22nd, https://www.githubstatus.com/incidents/83lq7ftk19r5 * on 23rd, https://www.githubstatus.com/incidents/tyc8wpsgr2r8 * on 24th, https://www.githubstatus.com/incidents/y5hdmv0p49x3

scaling is a hard problem to solve, so props to them for doing it without too much issues, overall.. but damn, since the microsoft acquisition, they are having more issues more frequently

Actions runs on Azure, actions were only possible with Microsoft.

Re: Incident with GitHub Actions

#26

Post by jameshush »

somehnacct3757 wrote: post #16

As the person who gets pinged when our CI isn't working, I'm hoping my next employer doesn't have github in their stack. We've reached the stage where architectural decisions are being questioned. Nobody should need to ask me "well why are we using github?" but here we are. They needed to fix this two weeks ago. The next time I'm in charge of stack decisions I will be evaluating competitors. This is exactly how Slack…

I'm curious, what's stopping you from hosting on-premise and/or using your own runners?

Re: Incident with GitHub Actions

#27

Post by K0nserv »

Shadonototra wrote: post #21
phoe-krk wrote: post #3

Previous GitHub incidents in March 2022: * on 16th, https://www.githubstatus.com/incidents/fpk08rxnqjz2 * on 17th, https://www.githubstatus.com/incidents/sksd097hm0y5 * on 22nd, https://www.githubstatus.com/incidents/83lq7ftk19r5 * on 23rd, https://www.githubstatus.com/incidents/tyc8wpsgr2r8 * on 24th, https://www.githubstatus.com/incidents/y5hdmv0p49x3

scaling is a hard problem to solve, so props to them for doing it without too much issues, overall.. but damn, since the microsoft acquisition, they are having more issues more frequently

Product development has also accelerated since the acquisition. Lots of interesting stuff has been released since it

Re: Incident with GitHub Actions

#28

Post by mschuster91 »

ricardobayes wrote: post #15
rydgel wrote: post #6

I'm glad we have a self-hosted Gitlab. Sure you need to do a bit of setup and configuration, but it's worth in the long run.

It's a bit of a weird thing as the whole word tries (or tried) to move away from on-prem stuff. Like Jira stopping support for non-cloud versions etc.

Probably Atlassian was sick of people never upgrading their old installations and getting hacked for it, and people did not upgrade because it is quite a hassle in the first place, not to mention plugins breaking allll the time.

Oh and because cloud forces continuous payment whereas prior many customers simply bought a one year license and went on without renewing support.

Re: Incident with GitHub Actions

#29

Post by sylware »

RapperWhoMadeIt wrote: post #11

I would maybe start migrating repos away from GitHub, since they have proven to be quite unreliable. Nonetheless, I must say I do appreciate GitHub's UI and even their CLI is quite nice. Is there a service out there that basically provides the same good user experience, CI/CD and has no costs for public repos? Apart from the unreliability I can't complain about GitHub.

github is still kind of friendly to noscript/basic (x)html browsers. I dunno how long it will last before $soft turns github into gitlab, namely explicitely hostile to noscript/basic (x)html browsers.

I did move my repos to "free" basic git hosting services on the net.

What would you need for today "development" (broad definition) of "popular" components: a web front end, an issue tracker, a mailing-list, a git server (ssh-ed write, http/https read).

The web front end is static html.

noscript/basic (x)html is beyond than enough for an "issue tracker" (cf bugzilla), including account creation (google javascript only-captcha is really nasty).

The mailing-list would need to implement grey listing for subscription (which would be disabled once the subscription process is done). The naive usage of spamhaus lists by many sysadmins of email servers is really toxic for self-hosted ppl or users of small email services.

The git server, well, the git server.

This is significant upfront work, not to mention the maintenance with the permanent "attacks" from corpo/state-sponsored paid/brain-washed saboters to deal with.

I understand why many devs are caving-in: they endup using those gitlab-like free and ready development hosting services because of the "path of least resistance". This is a very toxic pitfall, because those hosting services forces ppl to use the absurdely huge and grostesquely complex google(blink/geeko) or apple(webkit) based browsers where noscript/basic (x)html browsers should be more than enough for most, if not all, core online development functions.

Re: Incident with GitHub Actions

#30

Post by grumple »

RapperWhoMadeIt wrote: post #11

I would maybe start migrating repos away from GitHub, since they have proven to be quite unreliable. Nonetheless, I must say I do appreciate GitHub's UI and even their CLI is quite nice. Is there a service out there that basically provides the same good user experience, CI/CD and has no costs for public repos? Apart from the unreliability I can't complain about GitHub.

> Is there a service out there that basically provides the same good user experience, CI/CD and has no costs for public repos?

The answer is no. Other UIs are much worse in my experience. I haven't given Gitlab a good shake in a while though. That said, the network effects of Github are pretty significant. Everybody's on it, lots of major repos and orgs use it.

Post reply on HN