Matt Mitchell on DevOps on the .NET Core Engineering Services Team - Episode 63

Matt Mitchell is the lead engineer of the .NET Core Engineering Services Team at Microsoft. Matt joined Microsoft in 2006 after two years as an intern from 2004-05. Right out of the gate he did all C++ Compiler work for about 8 years. Eventually, his work morphed into working on the opensource infrastructure for .NET Core — which is what he's doing now!

In today's episode, Jeffrey and Matt are taking a look into DevOps on the .NET Core Engineering Services Team! Matt dissects what Engineering Services is and what they're responsible for, some of the different system types within .NET Core, an overview of the .NET Core infrastructure and how they go about building and testing, and much more! Tune in to hear all of Matt's key insights around .NET Core and the Engineering Services Team.

Topics of Discussion:

[:39] Be sure to visit AzureDevOps.Show for past episodes and show notes!

[:48] Jeffrey gives a few quick announcements.

[1:00] About today's guest, Matt Mitchell!

[1:20] Jeffrey welcomes Matt on to the show!

[1:26] Matt speaks about his career journey and how he landed his current position at Microsoft.

[3:02] Matt dissects what Engineering Services is, how it differs from .NET Framework Engineering Services Team and other teams, and what exactly they're responsible for.

[6:16] How many Git repositories overall make up .NET Core? And how do they organize that?

[13:58] Matt explains some of the different system types within .NET Core.

[17:11] With having 20 repositories now, does Matt foresee an event where they might have to introduce a 21st repository? And does his team provide guidance on how that would need to be set up if that was needed?

[20:05] A word from Azure DevOps Podcast's sponsor: Clear Measure.

[20:30] Jeffrey makes some announcements about upcoming events!

[21:09] Matt provides an overview of the .NET Core infrastructure and how they go about building and testing.

[26:00] Architecturally, the MS build tasks are the way that individual teams are provided with the tools to call so they don't have to duplicate that logic in their build scripts. So, for YAML files, is it just template guidance but that logic is duplicated in each repository?

[32:20] Matt explains why choosing the right number of repositories is one of the biggest ways to absolve some difficulties.

[35:16] Matt provides some examples of content-based systems.

[38:19] Matt recommends some resources to check out after listening to this week's podcast!

Mentioned in this Episode:

Azure DevOps

Clear Measure (Sponsor)

.NET DevOps Bootcamp 2020 — January 16th & 17th in Austin, T.X.

.NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Pre-order on Amazon here!

bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook!

bit.ly/dotnetdevopsbookforcommunity — Visit to get your hands on two free books to give away at conferences or events!

Jeffrey Palermo's Youtube

Jeffrey Palermo's Twitter — Follow to stay informed about future events!

"The Evolving Infrastructure of .NET Core," by Matt Mitchell (on the Microsoft .NET Blog)

Announcement of .NET Core Repository Consolidation

Timeline for Runtime Repository

Microsoft Phoenix

Midori

Roslyn Compiler
BuildXL GitHub Repository

Want to Learn More?

Visit AzureDevOps.Show for show notes and additional episodes.