2
Earu
3y

So we have this cycle of releases once every month for the products I work on at my company. Yesterday we started deploying a new version of one of our products on azure. Surprisingly it seems like none of the new features are working, and after two days of tweaking the code, deleting, moving, and re-publishing azure web jobs, rechecking the test environments, making sure every queue was used by the right webjobs… It turns out someone had published said webjob in 15 instances on a resource that we barely use and so the azure queue was being used by these outdated webjob instances…

Motherfucker, two days wasted for that :(

Comments
Add Comment