<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Devops on unop</title>
    <link>https://unop.uk/tags/devops/</link>
    <description>Recent content in Devops on unop</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-gb</language>
    <managingEditor>j.p.singleton&#43;blog@gmail.com (James Singleton)</managingEditor>
    <webMaster>j.p.singleton&#43;blog@gmail.com (James Singleton)</webMaster>
    <copyright>© James Singleton</copyright>
    <lastBuildDate>Wed, 11 Sep 2019 18:00:00 +0100</lastBuildDate>
    
	<atom:link href="https://unop.uk/tags/devops/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Getting Started with Azure DevOps CI - Chapter 5</title>
      <link>https://unop.uk/getting-started-with-azure-devops-ci-part-5/</link>
      <pubDate>Wed, 11 Sep 2019 18:00:00 +0100</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/getting-started-with-azure-devops-ci-part-5/</guid>
      <description>Continuous Delivery is not just about Continuous Integration (CI) but also about Continuous Deployment. I&amp;rsquo;ve covered CI over the previous posts in this series and now it&amp;rsquo;s time to deploy some releases using Azure DevOps.</description>
    </item>
    
    <item>
      <title>Getting Started with Azure DevOps CI - Chapter 4</title>
      <link>https://unop.uk/getting-started-with-azure-devops-ci-part-4/</link>
      <pubDate>Wed, 07 Aug 2019 18:00:00 +0100</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/getting-started-with-azure-devops-ci-part-4/</guid>
      <description>For this post in my series on performing CI with Azure DevOps I&amp;rsquo;ll be covering build pipelines using YAML code and why this is better than the old manual method.</description>
    </item>
    
    <item>
      <title>Getting Started with Azure DevOps CI - Chapter 3</title>
      <link>https://unop.uk/getting-started-with-azure-devops-ci-part-3/</link>
      <pubDate>Wed, 24 Jul 2019 18:00:00 +0100</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/getting-started-with-azure-devops-ci-part-3/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>Getting Started with Azure DevOps CI - Chapter 2</title>
      <link>https://unop.uk/getting-started-with-azure-devops-ci-part-2/</link>
      <pubDate>Wed, 17 Jul 2019 18:00:00 +0100</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/getting-started-with-azure-devops-ci-part-2/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>Getting Started with Azure DevOps CI - Chapter 1</title>
      <link>https://unop.uk/getting-started-with-azure-devops-ci/</link>
      <pubDate>Wed, 10 Jul 2019 18:00:00 +0100</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/getting-started-with-azure-devops-ci/</guid>
      <description>Azure DevOps is the latest re-branding of what used to be called VSTS (Visual Studio Team Services) and before that Visual Studio Online.</description>
    </item>
    
    <item>
      <title>Build and Release All Branches in TFS 2018 and VSTS</title>
      <link>https://unop.uk/build-and-release-all-branches-in-tfs-2018-and-vsts/</link>
      <pubDate>Sat, 17 Feb 2018 12:44:36 +0000</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/build-and-release-all-branches-in-tfs-2018-and-vsts/</guid>
      <description>Edit: VSTS is now called Azure DevOps but it&amp;rsquo;s essentially the same thing with a different UI. I have written an Azure DevOps guide series here.</description>
    </item>
    
    <item>
      <title>On AWS vs Azure, Vendor Lock-In and Pricing Confusion - Part 3</title>
      <link>https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-3/</link>
      <pubDate>Tue, 25 Oct 2016 10:01:00 +0000</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-3/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>On AWS vs Azure, Vendor Lock-In and Pricing Confusion - Part 2</title>
      <link>https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-2/</link>
      <pubDate>Tue, 18 Oct 2016 10:01:00 +0000</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-2/</guid>
      <description>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.</description>
    </item>
    
    <item>
      <title>On AWS vs Azure, Vendor Lock-In and Pricing Confusion - Part 1</title>
      <link>https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-1/</link>
      <pubDate>Tue, 11 Oct 2016 11:10:00 +0000</pubDate>
      <author>j.p.singleton&#43;blog@gmail.com (James Singleton)</author>
      <guid>https://unop.uk/on-aws-vs-azure-vendor-lock-in-and-pricing-confusion-part-1/</guid>
      <description>It&amp;rsquo;s about time that I wrote up my experiences using cloud hosting somewhere other than in a book. I&amp;rsquo;ve used both AWS and Azure extensively in a professional capacity.</description>
    </item>
    
  </channel>
</rss>