Azure Artifacts - Sprint 147 Update

Features

• Proxy support for Artifacts-related tasks
• Delegate who can manage feeds

Proxy support for Artifacts-related tasks

Until now, many Artifacts-related build tasks didn't provide full support for Azure Pipelines' proxy infrastructure, which led to challenges using the tasks from on-premises agents. With this update, we've added support for proxies to the following tasks:

• npm
• NuGet - restore and push commands only
• .NET Core CLI - restore and NuGet push commands only
• Universal Packages
• npm Authenticate, Pip Authenticate, Twine Upload Authenticate

  Note

  These tasks do not configure the proxy for the underlying tool (npm, pip, twine). They support proxies during the acquisition of auth tokens, but it is still necessary to configure any subsequent tasks/scripts/tools to also use the proxy.

• .NET Core Tool Installer, NuGet Tool Installer, Node.js Tool Installer

Delegate who can manage feeds

In Azure Artifacts, Project Collection Administrators (PCAs) have always been able to administer all feeds in an Azure DevOps organization. With this update, PCAs can also give this ability to other users and groups, thus delegating the ability to manage any feed.

Next steps

Note

These features will roll out over the next two to three weeks.

Head over to Azure DevOps and take a look.

Go to Azure DevOps

How to provide feedback

We would love to hear what you think about these features. Use the feedback menu to report a problem or provide a suggestion.

You can also get advice and your questions answered by the community on Stack Overflow.

Thanks,

Alex Mullans