<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Azure Repos on Engineering Leadership in AI &amp; Software</title>
		<link>https://engineering-leadership-preview.hinshelwood.com/tags/azure-repos/</link>
		<description>Recent content in Azure Repos 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-preview.hinshelwood.com/tags/azure-repos/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Branch Policies for TFVC</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/branch-policies-for-tfvc/</link>
				<pubDate>Wed, 13 Jan 2016 15:49:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/branch-policies-for-tfvc/</guid>
				<description>A new branch policy tool for TFVC allows you to apply policies like branch locks, code reviews, and work item requirements across multiple branches using simple patterns, making policy management much easier for large, complex codebases. This approach avoids cumbersome path-based setups and helps ensure key quality steps are not missed without overburdening developers. You can try the tool, provide feedback, or contribute to its development on GitHub.</description>
			</item>
			<item>
				<title>Create a Build vNext build definition</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/create-a-build-vnext-build-definition/</link>
				<pubDate>Wed, 04 Mar 2015 17:37:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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-preview.hinshelwood.com/articles/configure-a-build-vnext-agent/</link>
				<pubDate>Wed, 14 Jan 2015 14:55:00 +0000</pubDate>
				<guid>https://engineering-leadership-preview.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>Migrating source from Perforce to Git on VSO</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/</link>
				<pubDate>Wed, 20 Aug 2014 14:06:13 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/articles/migrating-source-from-perforce-to-git-on-vso/</guid>
				<description>Step-by-step guide to migrating source code from Perforce to Git on VSO, covering repository setup, dependency management, build processes, and key migration tips.</description>
			</item>
			<item>
				<title>Access denied for orchestration plan on Build</title>
				<link>https://engineering-leadership-preview.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-preview.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>Azure Repos</title>
				<link>https://engineering-leadership-preview.hinshelwood.com/tags/azure-repos/</link>
				<pubDate>Tue, 11 Feb 2025 10:17:24 +0000</pubDate>
				<guid>https://engineering-leadership-preview.hinshelwood.com/tags/azure-repos/</guid>
				<description>Azure Repos is a cloud-based source control service within the Azure DevOps ecosystem, designed to help teams manage their code repositories efficiently. It supports both Git and Team Foundation Version Control (TFVC), allowing teams to select the version control system that aligns with their specific workflows. By providing a centralised platform for code collaboration, Azure Repos integrates seamlessly with other Azure DevOps services, such as Azure Pipelines and Azure Boards, thereby enhancing the overall development lifecycle. Its significance lies in its ability to promote collaboration among team members, enabling concurrent work on code while minimising conflicts, which is essential for delivering value in a predictable and sustainable manner. Features like pull requests, branch policies, and code reviews help maintain code quality while facilitating rapid iteration and innovation. Additionally, Azure Repos fosters a culture of transparency and accountability by tracking changes and maintaining a clear history of contributions. This systemic approach to source control streamlines development processes and aligns with agile principles, promoting adaptability and responsiveness to change. By integrating with various tools and practices, Azure Repos empowers teams to focus on delivering high-quality software that effectively meets customer needs.</description>
			</item>
	</channel>
</rss>
