For my family I host a WordPress website on Azure (using an Azure App Service). I created it a while ago. At that time, Azure Database for MySQL Server (https://azure.microsoft.com/en-us/services/mysql) was not available yet, so the only choice was to host it at ClearDB (http://w2.cleardb.net/).
When using Visual Studio Team Services (VSTS) and Build/Release Agents, the way to authenticate is through Personal Access Tokens (PAT). A PAT can either expire in 90 days, 180 days or 1 year. The question is: what happens after expiration with my Build/Release Agent? Will it stop working? What if I restart it after expiration?
For one of my customers I had to migrate their current ProGet server to Visual Studio Team Services (VSTS) Package Management. That is because I am migrating them from TFS 2015 to VSTS. Although documentation is available, it wasn’t completely clear to me, so I wrote this blog.
Today I updated the utility I wrote which can help migrating a Visual Studio Team Services account from using Microsoft Accounts to start using Azure Active Directory accounts.
At a customer I’m implementing automated deployment for one of their web applications. We’re using a PowerShell DSC script that is kicked off by Release Management (which is part of Microsoft Team Foundation Server). Part of that script is a “File” resource which takes care of actually deploying the new files. Continue reading
When implementing a custom VSTS (or TFS) Build Task, it didn’t show up in the list of tasks after publish and install. Nor for Build, neither for Release. So I verified several options; Continue reading
For a customer I am analyzing the performance of the builds. They have Gated Check-in builds which take more than 30 minutes. The amount of Visual Studio Solutions built varies from 8 to 12. I need to know which part of the Build takes most time. Continue reading
