I’ve also created a build plan in Azure Pipelines that generates a .nupkg file from a .nuspec definition using nuget pack. That’s actually working great and Orchestrator is able to run that .nupkg file and I’m quite happy with that. But, I would like to run my unit tests during the build. I’ve altered that framework to output a junit valid results .xml file that Azure Pipelines can parse. The framework has a RunAllTests.xaml file that runs all of the unit tests.
The issue is that I need the UiPath Robot to run that file which I don’t have access to in Azure Pipelines. An idea: If I could install robot.exe on my Azure Pipelines agent (the machine that runs the build plan), I could run the RunAllTests.xaml file using that. My question with this is licensing, would I need to pay for a license to use the Robot.exe file on my agent? How can I feed parameters to the Robot.exe file to execute the RunAllTests.xaml file specifically?
You don’t need to license the robot from the build agent machine as long at it is utilized to build nuget packages and not to run automation processes.
@kellen, the Azure DevOps integration Clayton is talking about can be found here in case you didn’t find it yet.
We are also investigating this issue and I would love to hear more from anybody already doing it. I’m particularly interested in any modifications to adapt the framework to operate within the build/release pipeline, and how to return its results/metrics.
Bogdan_Popescu, you write: " You don’t need to license the robot from the build agent machine as long at it is utilized to build nuget packages and not to run automation processes." I take this to mean that a license is not needed to build the .NuPkgs on the build agent. But what we are talking about here is, specifically, then executing an automation process on this agent (tho what the automation is doing is not, strictly speaking, a workflow), so am I correct in concluding that a license is required?