Since today we are getting the following error:
##[error]No agent found in pool RPA-Pool which satisfies the specified demands: npm, Agent.Version -gtVersion 2.144.0
Any advice how to fix it?
Fixed it, by creating the folder âC:\users[user]\apdata\roaming\npmâ and add that folder to the agent as capability
2 Likes
We were receiving an error because we donât have UiPathTest license. After removing that task, the issue was resolved.
Dear All,
I am facing the same error. Any update how to solve it?
##[error]Error deploying package: Error: The process âC:\Program Files\dotnet\dotnet.exeâ failed with exit code 1.
Please share the update anyone.
Hi Thomas, we are now figuring out the automatic deployment for libraries. It is not clear what Folder we need to specify in Deploy step when we deploy Libraries into Tenant feed and not a specific folder?
How to add release note to the UiPath package published via ADO pipleline or how to use the last commit message itself as a release notes text?
Hello @Ishwar_P_S,
Unfortunately there is not possible to do this currently.
But we will cover this in our next release. 
Stay tuned!
1 Like
Hello @NikitaSolodovnikov,
Any folder in your tenant should do the trick when deploying Libraries, as the CLI would understand that the package you are trying to deploy is of Libraries type and would deploy it on the Tenant feed.
Iâve noted this scenario and we will improve this for our ADO Extension in a future release.
Thanks!
In the best interest of your questions please start a new thread for each topic that you might have as we can follow up on each problem specifically.
Thank you,
AutomationOps Team!
Any update on this, this is very important for support team members to identify quickly from the package tab itself and switch between the the packages or to know which package has what change
With the latest release of the Azure DevOps tasks we have added ability of setting of Release notes to a package and also from the previous version you can set the commit id on the package.
More details here: Automation Ops - Azure DevOps Extension Release Notes
1 Like
That sounds great.
Finally some form of traceability in Orchestrator packages deployed from Azure Devops. My team is very glad that this is a reality now.
1 Like
Is there any plan to allow for custom workflow analyzer rules to be checked against during the pack task?
Or, even better, having a separate pipeline task dedicated just to Workflow Analyzer/Governance?
Hi @nickboswell ,
In the 5.* version of the Azure DevOps tasks we included the ability to pass the path to the governance file containing the workflow analyzer rules.
See the underlying uipcli arguments described here: Automation Ops - Executing Tasks
1 Like
Is there any updates regarding the UiPath integration incl. the different built-in tasks that uses a end-of-life Node 10 version using hosted/free windows agents?
@ThomasStocker @alexandru.iordan @CristianCotovanu
Weâre getting the following warning running our Azure Pipelines.
##[warning]Task âUiPath Install Platformâ version 4 (UiPathInstallPlatform@4) is dependent on a Node version (10) that is end-of-life. Contact the extension owner for an updated version of the task. Task maintainers should review Node upgrade guidance: Add a build or release task in an extension - Azure DevOps | Microsoft Learn
Thank you for raising this. We started to look into this, but I donât yet have a release date with the fix.