Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow specifying a particular NPM registry for TfxInstaller task to use #489

Closed
Porges opened this issue Jan 31, 2025 · 3 comments
Closed

Comments

@Porges
Copy link
Member

Porges commented Jan 31, 2025

See comments over here for more background: #476 (comment)

It would be useful if TfxInstaller provided a registry option to select which NPM registry to install from. At the moment TfxInstaller is unusable in some configurations where (for example) npmjs.org is blocked.

(Auth should also automatically happen for this registry if it's in the same ADO project, just like in the Npm@x task.)

@jessehouwing
Copy link

This relates to: https://github.com/microsoft/azure-devops-extension-tasks, not tfs-cli.

@jessehouwing
Copy link

You can always manually populate the Tools cache folder, the TfxInstaller task will pick this up.

@Porges
Copy link
Member Author

Porges commented Feb 4, 2025

This relates to: https://github.com/microsoft/azure-devops-extension-tasks, not tfs-cli.

Will migrate it to there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants