← Back to context

Comment by wnevets

6 days ago

> Their entire ecosystem is basically held up with duct tape and gets very little investment.

That isn't gonna get better anytime soon.

"GitHub Will Prioritize Migrating to Azure Over Feature Development" [1]

[1] https://thenewstack.io/github-will-prioritize-migrating-to-a...

8 comments

wnevets

Reply
amarant  6 days ago

Hey at least we can all expect lots of extra days off because "GitHub is down" once they're done with that migration!

  • phantasmish  6 days ago

    They had working infra and a great case for keeping fairly "close to the metal". Complicated files-heavy workload that needs tons of clever caching to perform well, lots of writes, lots of non-HTTP TCP traffic.

    Retrofitting that into "cloud" bullshit is such a bad idea.

    • theamk  6 days ago

      meh, I dunno.

      Using bare-metal requires competent Unix admins, and Actions team is full of javascript clowns (see: decision to use dashes in environment variable; lack of any sort of shell quoting support in templates; keeping logs next to binaries in self-hosted runners). Perhaps they would be better off using infra someone else maintains.

      2 replies →

gregoryl  6 days ago

They barely maintain Azure pipeline tasks / actions as well.

We had a critical outage because they deprecated Windows 2019 agents a month earlier than scheduled. MS support had the gall to both blame us for not migrating sooner, and refuse to escalate for 36 hours!

  • drysart  2 days ago

    What? No they didn't. They extended the deprecation timeline for Windows 2019 agents from the original EOL date of 30 June 2025 to 31 December 2025; with a well-published brownout period from 2 December to 9 December in addition to the original brownout period from 3 June to 24 June.

    The initial banners and warning emails about it went out well ahead of the original EOL timeline; and again as the extended EOL drew close.

    If you were caught off guard by the brownout period, it's your devops team that's to blame, not Microsoft; and Microsoft was absolutely right to blame you for not migrating sooner. They gave you an extra 6 months to do it because you should have had all this done back in the first half of the year.

    (If you want to blame Microsoft for anything here, blame them for not having a comprehensive tool to identify all your windows-2019 pipelines and instead just relying on "just go look at the latest pipeline runs page and hope everything's run recently enough to be on that".)