I'm excited to announce the public previews of pipeline caching and pipeline artifacts in Azure Pipelines. Together, these technologies can make every run of your pipeline faster by accelerating the transfer of artifacts between jobs and stages, and by caching the results of common operations like package restores.
Azure Artifacts introduces pay-per-GB pricing and is available to all users in your organization - no license needed. Also, Python and Universal Packages are generally available and ready to use at scale.
For a long while, Azure Pipelines users have been asking to improve performance on the hosted build agents by adding caching for common scenarios like package restore. The issue came up in a recent popular Hacker News item, so we wanted to share an update.
Until now, Package Management has hosted packages that are part of a development ecosystem: NuGet packages for .NET development, npm packages for Node.js and web frontend development, and Maven packages for Java development. We’re also continuing to expand our support for new development ecosystem,
Software packages are a crucial part of development in languages ranging from C# to JavaScript to Python to Go. They help you iterate faster, avoid solving a problem that’s been solved many times before, and allow you to focus on your unique value.
Until now, we’ve focused on making Package Management in Visual Studio Team Services and Team Foundation Server the best place to store your private NuGet and npm packages, but we haven’t focused as much on the packages you use from public sources like NuGet.org.
As far back as 2012, Visual Studio Team Services and Team Foundation Server users have been asking for a Symbol Server. Symbols are crucial to debugging Windows applications, esp. applications written in native languages like C and C++, because they map from the built binary back to the source code: the classes and functions needed to step through an application line-by-line.
NuGet (both the command-line tool and the accompanying tools built into Visual Studio) continues to iterate rapidly and add support for new .NET Core and .NET Standard target frameworks, among other improvements. Naturally, many users of Team Build in Visual Studio Team Services want to build those apps,
We know that packages are a key way to bring in dependencies and to share your work with your users, and we know many of you are using private package sources (like Package Management, Artifactory, MyGet, and others) to develop packages inside your organization.
Today, I’m proud to announce that Package Management is generally available for Team Services and TFS 2017! If you haven’t already, install it from the Visual Studio Marketplace.
Best-in-class support for NuGet 3
NuGet support in Package Management enables continuous delivery workflows by hosting your packages and making them available to your team,
