25.10.18

公開日: 2026 年 5 月 27 日

更新内容

Your nuget.config is now fully respected

If you pass a nuget.config file with --nugetConfigFilePath, the CLI now honors everything inside it — not just the list of feed URLs. Previously, only the <packageSources> URLs were applied, which meant Basic-auth feeds like JFrog failed with 401 Unauthorized because their credentials were silently dropped. With 25.10.18, the following common scenarios work out of the box:

• Private feeds that require a username and password (JFrog, Sonatype Nexus, internal Azure Artifacts). Put the credentials in the same file under <packageSourceCredentials> and you're done — no extra CLI flags needed. The 401 Unauthorized failures customers hit on previous CLI versions are resolved.
• Ignoring the build agent's own NuGet configuration. Add <clear /> at the top of <packageSources> and only the feeds you declare in this file are used.
• Routing specific packages to specific feeds. Use <packageSourceMapping> to send, for example, UiPath.* packages to your internal mirror and everything else to a public feed.
• Air-gapped or offline builds. Use <fallbackPackageFolders> to point at a local folder of pre-downloaded packages.

Example — a private feed protected by a token, with a local folder used as a fallback:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
  <packageSources>
    <clear />
    <add key="UiPath-Internal" value="https://artifactory.contoso.example/api/nuget/v3/uipath-feed/index.json" protocolVersion="3" />
  </packageSources>

  <packageSourceCredentials>
    <UiPath-Internal>
      <add key="Username" value="ci-bot" />
      <add key="ClearTextPassword" value="%ARTIFACTORY_TOKEN%" />
    </UiPath-Internal>
  </packageSourceCredentials>

  <fallbackPackageFolders>
    <add key="OfflinePackages" value="C:\ci\offline-packages" />
  </fallbackPackageFolders>
</configuration>

uipcli package pack "C:\projects\MyProject\project.json" -o "C:\Output" \
  --nugetConfigFilePath "C:\ci\nuget.config"

Inject the password through a CI secret — the %ARTIFACTORY_TOKEN% placeholder is read from the environment at runtime.

If you previously had to combine --nugetConfigFilePath with --disableBuiltInNugetFeeds or --excludeConfiguredSources to keep the build agent's feeds out of your restore, you can now achieve the same result with just <clear /> inside the file. Both approaches still work — pick whichever is simpler for your pipeline.

Test Manager no longer times out on large test runs

uipcli test run --projectKey previously failed on very large test sets because preparing the test set on the Test Manager side took longer than a single HTTP call allows. The CLI would surface a timeout error even though Test Manager had accepted the request and was still working on it.

Starting with 25.10.18, the CLI waits for Test Manager to finish preparing the test set before moving on to execution. While it waits, the console prints a periodic status message such as:

Test set creation is still in progress, retrying in 5 seconds...

You don't need to change anything in your pipeline — the new behavior applies automatically to every test run --projectKey invocation, whether you reference an existing test set with --testsetkey or create a transient one from a project path with -P.

uipcli test run "https://cloud.uipath.com/" "TenantName" \
  --projectKey "MyTestProject" \
  --testsetkey "MyLargeTestSet" \
  -A "organizationName" \
  -I "becc663c-8f1e-409a-a75f-c00330d80bc8" \
  -S '********' \
  --applicationScope "OR.Folders OR.Execution TM.Projects TM.TestSets TM.TestExecutions" \
  -o "FolderName" \
  --out "junit" \
  --result_path "./test-results"

ドキュメントの更新

• NuGet フィードを管理する
• Test Manager でパッケージをテストする、またはテスト セットを実行する
• プロジェクトをパッケージ化する
• オートメーションの依存関係を復元する
• プロジェクトを分析する
• ソリューションを梱包する
• パッケージをテストするか、テスト セットを実行する
• 複数のパッケージをテストする