I'm very excited to finally be able to talk publicly about Azure DevOps which was announced today. Azure DevOps is a set of services which includes:

Azure DevOps represents the continued evolution of Visual Studio Team Services and includes all of its existing functionality. Even though all of the services in Azure DevOps work well together, this change makes it easier to acquire individual elements of Azure DevOps and adopt the rest at your own pace.

When you acquire one of the Azure DevOps services, you are guided through the process of creating an Organization (formerly called an Account). Once you have an Organization you can enable or disable the other Azure DevOps services easily in the project settings.

I think that this is a great new model, because if I am using GitHub to host the source of my project, I can pick up just Azure Pipelines to take care of my CI/CD requirements (by the way, GitHub announced that Azure Pipelines is available via the GitHub Marketplace). Exciting times!

Introducing Azure Artifacts

The Azure DevOps service that I work on is Azure Artifacts. Azure Artifacts includes Feeds for NuGet, NPM, and Maven packages but also includes symbol hosting. Over the coming months we'll be adding even more functionality to Azure Artifacts.

Two new artifact types that we'll be adding in the near term are Universal Packages and Pipeline Artifacts - both of which are built on top of technology we use within Microsoft to handle large scale artifacts. I'll be blogging about these in a bit more detail when we go into preview.

Learn More at TechBash

If you want to know more about Azure DevOps I am going to be giving a workshop with Paul Hacker at TechBash 2018 on DevOps with Visual Studio Team Services ... guess we should update the title of the session now :)