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

Unable to install tfx-cli using yaml task in Azure Devops Pipeline - TfxInstaller@4 #476

Closed
v-gpriyanshu opened this issue Nov 4, 2024 · 4 comments

Comments

@v-gpriyanshu
Copy link

Whenever we try to install tfx-cli using TfxInstaller@4 task, error persists : "Unable to find Tfx version". We tried we every other version, it's not working. Here is the task :-

  • task: TfxInstaller@4
    inputs:
    version: 'v0.x'

Image

@ivanduplenskikh
Copy link
Contributor

@v-gpriyanshu, I noticed that your screenshot shows the extension v3, yet in your message, you referred to TfxInstaller@4. Could you kindly clarify which version is currently in use?

I've successfully installed [email protected] using TfxInstaller@4 on my test organization.
Image

@ivanduplenskikh
Copy link
Contributor

I'm closing this issue. Feel free to reopen if you have any additional questions.

@Porges
Copy link
Member

Porges commented Jan 30, 2025

@ivanduplenskikh I can confirm the same behaviour with v4 and v5. Neither of these can install any of v0.17.x, 0.17.x, 0.17 or v0.17. Something seems to be not working properly and I can't see any logs indicating what the problem is.

@Porges
Copy link
Member

Porges commented Jan 31, 2025

I think what's going on here is that the MS Build Network Isolation policies are currently being rolled out on ADO pipelines. This means that TfxInstaller cannot contact npmjs.org, and installation is failing. However, does not provide a way to override which registry it is reading from (and does not produce log output when this happens).

At the moment I'm trialling a workaround by installing tfx-cli myself and then setting the secret __tfxpath variable manually to convince the extension publishing task to run. (Edit: confirmed that this works – __tfxpath should point to the parent directory containing the npm-installed script.)

Edit 2: actually a better thing to do would be npm config --global set registry=REGISTRY before the TfxInstaller task, but for some reason that doesn't seem to take effect.

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

3 participants