Share your packages stored in Azure DevOps with guests and anonymous users with the public preview of public feeds.
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.
At the end of last sprint we flipped the switch on a new feature for Azure Artifacts called Universal Packages. With Universal Packages teams can store artifacts that don’t neatly fit into the other kinds of package types that we support. A Universal Package is just a collection of files that you’ve uploaded to our service and labelled with a name and version.
On the 24th of July 2018, we notified some customers via e-mail and on this blog about a planned action that we would start taking in relation to the malicious ESLint NPM package incident. This action is now underway.
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,
To demonstrate our continued commitment to support Java developers and their full lifecycle DevOps needs with Visual Studio Team Services (VSTS) and Team Foundation Server (TFS), I want to share some of our recent and exciting Java-related feature announcements. Our teams are working with large and small Java teams every day to better understand their needs and to solicit recommendations for improvements of our tools.