Bot can't find Nuget package in ADO feed. Looks in orchestrator instead

[Freymish (Jack Handy)]

I have a group of helper apps that I created to do housekeeping, MFA email search and code extraction, intialize variables from config files, etc. I have been publishing these to my ADO project feed for over a year. I recently iupdated the underlying activities to the latest versions and republished the NuGet package to ADO but the robot can’t find the version. It is looking for it in Orchestrator instead of ADO (or perhaps after trying the first location?) Anyway, I noticed this error:

UiPath.CoreIpc.RemoteException: NU1102: Unable to find package FailureTeardown with version (= 1.2.0)

• Found 1 version(s) in UiPath…-…-f35aeeaea1e0/index.json [ Nearest version: 1.0.26 ]
• Found 0 version(s) in Local
• Found 0 version(s) in nuget.org
• Found 0 version(s) in Connect
• Found 0 version(s) in https://pkgs.dev.azure.com/uipath/Public.Feeds/_packaging/UiPath-Official/nuget/v3/index.json
• Found 0 version(s) in Official
  — End of inner exception stack trace —

I had once published the 1.0.26 version to that location in the past but I have been running the ADXO feed versions for a long time now. I went ahead and published the 1.2.0 version to Orchestrator and was able to run the job. I shouldn’t have had to do that. Anybody know why that might have happened? Is this a bug?

[Anil_G (Anil Gorthi)]

@Freymish

Is the ado feed present in the package feeds of robot?

Robot - Configuring activity feeds

Or do you have a cicd setup which pushes package to orchestrator once you add to ado

Cheers

[Freymish (Jack Handy)]

The ADO source feed is in the nuget.config for the bot account on the job servers. (Is there some other location this should be referenced? The servers only run the bot service.) This has been working normally for well over a year. I am not currently publishing this particular package to the Orchestrator and never have except once about a year ago.

[marian.platonov]

There was a documentation for that on how to disable the built-in feeds when packaging an automation project and use a custom nuget.config file where you had your sources.

Automation Ops - Azure DevOps Extension Release Notes

[Freymish (Jack Handy)]

I checked that out and although it says you can do it, it doesn’t say how. Where can I set that value?

[marian.platonov]

The custom nuget.config file to pull the custom feeds needs to be added at the root of the CLI.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="test custom feed" value="custom_feed_url" />
  </packageSources>
</configuration>

ADO

After InstallPlatform copy nuget.config to $(Agent.ToolsDirectory)/uipcli:

trigger:
- main

pool:
  vmImage: ubuntu-latest

stages:
- stage: Demo
  jobs:
    - job: Demo
      steps:
        - task: UiPathInstallPlatform@5
          inputs:
          cliVersion: 'WIN_23.10.9076.19285'
        displayName: 'Installing UiPath CLI'
        
        - task: CopyFiles@2
          inputs:
            SourceFolder: '$(Build.SourcesDirectory)'
            Contents: 'nuget.config'
            TargetFolder: '$(Agent.ToolsDirectory)/uipcli'

        - task: UiPathPack@5
          inputs:
            versionType: 'AutoVersion'
            projectJsonPath: '$(Build.SourcesDirectory)/AutomationProjects/CrossPlatform/VB/ProjectWithCustomLibraryFromOrchestrator_CrossPlatform_VB/project.json'
            outputPath: '$(Build.ArtifactStagingDirectory)/Output'
            disableBuiltInNugetFeeds: true
            traceLevel: 'Verbose'

[Freymish (Jack Handy)]

I am not running this as pipeline build. I am building it on my machine and publishing it directly to Orchestrator from there. I have been doing this exact thing for a few years now. In addition, it is only in the past week that this started happening. Prior to this last published build of the NuGet pkg it worked as it always has.

[marian.platonov]

If you are using the plain CLI follow these:

To complement existing nuget.config files, create another nuget.config file and place it somewhere in the folder hierarchy of the uipcli.exe like in the attached screenshot.

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <add key="test custom feed" value="custom_feed_url" />
  </packageSources>
</configuration>

Then try to run the CLI and observe if your custom feed appears in the logs.

[Freymish (Jack Handy)]

Well, I did get this resolved but I can no longer remember how. I’m a dummy! I think I did it by deleting and re-creating the NuGet.config and reentering all the values for my connections.