Continuous Delivery is not just about Continuous Integration (CI) but also about Continuous Deployment. I’ve covered CI over the previous posts in this series and now it’s time to deploy some releases using Azure DevOps. »
For this post in my series on performing CI with Azure DevOps I’ll be covering build pipelines using YAML code and why this is better than the old manual method. »
This was going to be a post about how to perform CI builds on Azure DevOps but there can be so many issues just hosting your code that I thought I should expand upon that first. »
This post follows on from my previous one on getting started with Azure DevOps. Read that first if you have yet to create an organisation, project or repository. »
Azure DevOps is the latest re-branding of what used to be called VSTS (Visual Studio Team Services) and before that Visual Studio Online. »
Edit: VSTS is now called Azure DevOps but it’s essentially the same thing with a different UI. I have written an Azure DevOps guide series here. »
This is the final part of my three part cloud trilogy: AWS vs Azure Lock-in Pricing (this post) Pricing As mentioned in the first post in this series, cloud hosting may not be the best value option for you. »
This is part two of my three part cloud trilogy: AWS vs Azure Lock-in (this post) Pricing Lock-In Cloud hosting can be very convenient and some of the value-add services that are offered on top of the basic packages can save a lot of time. »