<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Azure Pipelines on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/</link>
		<description>Recent content in Azure Pipelines on Engineering Leadership in AI &amp; Software</description>
		<generator>Hugo</generator>
		<language>en</language>
		
		
		
		
			<lastBuildDate>Tue, 16 Jun 2026 17:40:35 +0000</lastBuildDate>
		
			<atom:link href="https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>The High of Release</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/the-high-of-release/</link>
				<pubDate>Sat, 05 Dec 2015 14:49:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/the-high-of-release/</guid>
				<description>Microsoft’s new web-based Release Management tools let teams build flexible, integrated release pipelines in VSTS or TFS without being locked into specific deployment tools. The focus is on orchestration and integration, allowing you to use your preferred technologies like Chef, Puppet, Docker, or PowerShell. These tools are now in public preview, so consider evaluating them to streamline your release process and support cloud or on-premises deployments.</description>
			</item>
			<item>
				<title>Create a Release Management pipeline for Professional Developers</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/</link>
				<pubDate>Thu, 04 Dec 2014 12:15:56 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/create-a-release-management-pipeline-for-professional-developers/</guid>
				<description>This guide walks through setting up an automated release management pipeline using TFS/VSO and Azure, showing how to build, deploy, and parameterize a legacy web app across multiple feedback environments. Key takeaways include the importance of automating builds and releases, using environment-specific parameters, and streamlining approvals for smoother deployments. Development managers should consider investing time upfront to automate and parameterize their pipelines, as this reduces manual errors and accelerates feedback cycles.</description>
			</item>
			<item>
				<title>Create a Build vNext build definition</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/create-a-build-vnext-build-definition/</link>
				<pubDate>Wed, 04 Mar 2015 17:37:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/create-a-build-vnext-build-definition/</guid>
				<description>Microsoft&amp;rsquo;s new Build vNext system for TFS and VSO is more modular and user-friendly, offering a wide range of out-of-the-box build and deployment tasks, improved configuration options, and better auditability of changes. It currently supports only Git repositories and continuous integration triggers, with plans for greater extensibility and additional features in the future. Development managers should consider evaluating Build vNext in test environments to prepare for its eventual adoption and to explore its enhanced flexibility and control.</description>
			</item>
			<item>
				<title>Configure a Build vNext Agent</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/configure-a-build-vnext-agent/</link>
				<pubDate>Wed, 14 Jan 2015 14:55:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/configure-a-build-vnext-agent/</guid>
				<description>Microsoft&amp;rsquo;s new modular build system for TFS and VSO, currently in early preview, replaces the old controller model with a more flexible pool and queue approach, simplifying agent management and permissions. Setting up a vNext Build Agent requires spinning up your own VM, installing Visual Studio 2013 or 2015, and configuring the agent via PowerShell. Development managers should prepare for a shift to this new system and consider early testing to understand its benefits and requirements.</description>
			</item>
			<item>
				<title>Access denied for orchestration plan on Build</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/</link>
				<pubDate>Wed, 16 Dec 2015 14:18:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/access-denied-for-orchestration-plan-on-build/</guid>
				<description>When setting up a TFS build agent for a high-volume customer, a permissions error blocked builds because the &amp;ldquo;Project Collection Build Service&amp;rdquo; lacked write access to the orchestration plan. The issue is tied to permission inheritance and a known bug in TFS 2015 RTM, and can be fixed by ensuring both &amp;ldquo;Project Build Service&amp;rdquo; and &amp;ldquo;Project Collection Build Service&amp;rdquo; have inherited permissions on build definitions via Visual Studio. Development managers should verify these permissions to avoid similar build failures and streamline onboarding to new build systems.</description>
			</item>
			<item>
				<title>How to deal with a stuck or infinitely queued build</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/how-to-deal-with-a-stuck-or-infinitely-queued-build/</link>
				<pubDate>Thu, 09 Sep 2010 12:59:23 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/how-to-deal-with-a-stuck-or-infinitely-queued-build/</guid>
				<description>Learn how to identify, troubleshoot, and resolve stuck or infinitely queued builds in Team Foundation Build, including tips for monitoring and restarting build services.</description>
			</item>
			<item>
				<title>Reserve an Agent for a special build in Team Foundation Server 2012</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/</link>
				<pubDate>Thu, 04 Apr 2013 01:37:57 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/reserve-an-agent-for-a-special-build-in-team-foundation-server-2012/</guid>
				<description>Explains how to reserve a build agent in Team Foundation Server 2012 using custom activities, agent tagging, and workflow changes to ensure reliable, isolated build execution.</description>
			</item>
			<item>
				<title>Using the Build vNext capabilities and demands system</title>
				<link>https://engineering-leadership.hinshelwood.com/articles/using-the-build-vnext-capabilities-and-demands-system/</link>
				<pubDate>Wed, 11 Mar 2015 14:10:00 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/articles/using-the-build-vnext-capabilities-and-demands-system/</guid>
				<description>Build vNext in TFS 2015 introduces a capabilities and demands system that replaces the old agent tagging approach, making it easier to match build agents to specific build requirements. Agents now auto-detect many capabilities, and you can add custom ones like OS version to ensure builds run on suitable machines. This streamlines build configuration and targeting, so managers should explore Build vNext to improve build reliability and agent management.</description>
			</item>
			<item>
				<title>Azure Pipelines</title>
				<link>https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership.hinshelwood.com/tags/azure-pipelines/</guid>
				<description>Azure Pipelines is a cloud-based service designed to automate the processes of building, testing, and deploying applications, thereby enabling teams to deliver value in a predictable and sustainable manner. Originating from the need for efficient software development practices, it integrates seamlessly with various version control systems to facilitate continuous integration and continuous delivery (CI/CD). This capability allows teams to implement code changes frequently and reliably, significantly reducing manual errors and accelerating feedback loops while enhancing collaboration among cross-functional teams. The importance of Azure Pipelines lies in its ability to streamline workflows and improve overall efficiency throughout the software development lifecycle, supporting a diverse array of programming languages and platforms to meet varied project needs. By offering a consistent framework for managing builds and releases, it promotes a culture of continuous improvement and innovation. Furthermore, its integration with Azure DevOps tools, such as Azure Boards and Azure Repos, fosters a cohesive project management environment that enhances visibility into the development process and aligns teams towards shared objectives. This systemic approach ultimately drives organisational agility and resilience, with long-term benefits including increased deployment frequency, reduced lead times, and a heightened focus on delivering high-quality software that aligns with customer requirements.</description>
			</item>
	</channel>
</rss>
