Hacker News Reader

Comment by sli | Hacker News Reader

A previous employer switched everything over to Azure and it was nothing but constant problems and nobody liked it except for the CEO, which meant everyone had to put up with it and nobody had a say.

Teams and Azure DevOps are some of the worst software I've ever used in my life. I've used worse software before, but it was hobbyist stuff written by single developers, and therefore don't really compare fairly.

View on HN

At a previous company I used slack and really liked it. At this new company I joined recently they use Teams and it felt like a ghost town. Nobody online and nobody communicating in public.

The reason is that it’s impossible with the desktop app to browse channels that you’re not a member of, whereas on mobile you can! When I mentioned it to my colleagues they were shocked. This whole time they could have been communicating in other channels and they had no idea they existed. I have no idea if this is a bug, or some kind of admin setting.

There are plenty of other issues with DevOps too. You have to buy in to the whole Microsoft package apparently, and none of the parts are best in class.

Huh, I’ve used Skype for business before, and Teams is definitely better.

The problem with Teams is that companies use it to replace Slack, which is much more pleasant to use.

Azure Pipelines is just slow. I'm not sure even how to fix it.

Checkout stage of our code from Azure Repos easily count for half a minute. Npm install goes for a 1.5 minute with npm cache hit. Total build times are around 20 minutes...

there is an undocumented feature, called zip deploy, if you deploy to an app service. Give it a go, it might just work. I use it to deploy a Python Django website. You need to add a setting in your App Service environment variables.

It took me an escalation from our account manager, to get a good support guy, who informed me of this functionality.

Here is the summary of my support ticket:

WEBSITE_RUN_FROM_PACKAGE” and value as 1.

We performed deployment and it took around 30 secs. We also verified that the app is working fine.

Now you will do some changes and deploy once more to verify end to end pipeline.

Zip deployment is a feature of Azure App Service that lets you deploy your function app project to the wwwroot directory. The project is packaged as a .zip deployment file. The same APIs can be used to deploy your package to the d:\home\data\SitePackages folder. With the WEBSITE_RUN_FROM_PACKAGE app setting value of 1, the zip deployment APIs copy your package to the d:\home\data\SitePackages folder instead of extracting the files to d:\home\site\wwwroot. It also creates the packagename.txt file. After a restart, the package is mounted to wwwroot as a read-only filesystem.

Article for reference: https://docs.microsoft.com/en-us/azure/azure-functions/run-f...

Azure Devops is clearly not being actively developed, or there is no way it would remain so bad for so long.

Simple things like being able to sort tables un the web UI have had open issues for years.

Reply on news.ycombinator.com