Reply to post: Re: During the meanwhile ...

Asleep at the wheel: Why did it take 5 HOURS for Microsoft to acknowledge an Azure DevOps TITSUP*?

Anonymous Coward
Anonymous Coward

Re: During the meanwhile ...

In steady state, yes. Just out of interest though, if a new team has a requirement for additional build nodes for their their CI/CD pipeline, or a new project starts up with a major new build requirement, how long does that currently take you to fill, from the moment the ticket is filed to them being fully operational? How long is it if your virtual infrastructure is full, and you need to procure more servers? How long if your datacentre is near full, and you prioritise production environment capacity demands?

Perhaps your environment is different, with great capacity management, managers who are prepared to fund significant spare capacity ahead of known demand, and suppliers who don't let you down. But I've seen teams stuck for months with hugely inadequate CI/CD capacity in large enterprise environments, with massive impacts on productivity - far more than a day or so's Azure DevOps outage would have. The old-school workaround of sticking beefy tower PCs under half the teams' desks and running the Jenkins jobs through those tends to be (rightly) blocked by security nowadays, so it's a real issue.

Don't get me wrong though, the Microsoft outage was still shit.

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon

SUBSCRIBE TO OUR WEEKLY TECH NEWSLETTER

Biting the hand that feeds IT © 1998–2020