UiPath Azure Devops Integration

Robotic Process Automation is software and should be treated the same way. Therefore we try to support you in integrating your RPA development and Testing into your existing CI/CD pipeline.

Besides our native Jenkins Plugin, we have just released the latest version of our AzureDevops integration, which allows you to…

  • Package UiPath projects
  • Deploy packages to Orchestrator
  • Run Test Cases on Orchestrator.

Please feel free to give it a try and provide feedback.

Here is a quick tutorial on its usage:

  1. Setup a Service Connection in AzureDevops, that allows you to communicate with Orchestrator
    To do this…
  • go to Project Settings image
  • select Service Connections
    image
  • select New Service Connection
    image
  • Select UiPath Orchestrator Connection
    image
  • Provide details for URL and authentication and store it
  1. Create a pipeline
  • Click on Pipelines
    image
  • Select New pipeline
    image
  • Link it with your code repostiroy
  1. Add the UiPath Integration steps
  • Select your pipeline and click on Edit
    image
  • in the tasks bar search for UiPath
    image
  • Select the task you want to use and configure it accordingly.
    (A detailed documentation on the available tasks and configurations can be found here)

BR, your Product Team

8 Likes

Hi there @ThomasStocker,
This new release looks amazing!

We recently moved across to this, however, we noticed that the deploy functionality does not discern between a Process Project and a Library Project.

As such, all get put into the Packages feed, as opposed to being segmented between Packages and Libraries.

Is this intended, or a bug?
Thanks in advance for your support,
Josh

1 Like

Hi,
thx a lot for your feedback!
You are right, we should be able to distinguish between libs and standard packages here. We have logged your request and will try to deliver it in the upcoming version.

1 Like

Amazing, thanks @ThomasStocker!

This feature would make the extension perfect for us :slight_smile:

Do you think this could be done in two phases?
For the first, simply provide the parameter and let us note the type, either by parsing the project.json ourselves or by simply hard-coding it - Then deploy to the selected feed.

In the second phase, have the extension ascertain the type and deploy appropriately.

Just excited and want to start leveraging it ASAP!
Thanks once again for your support,
Josh

1 Like

We have not figured that out, but your input is definitely valuable. Will let you know when this is available.

1 Like

Really nice to see progress on the Azure DevOps Plugin. Working good for me!

Only thing what i don’t get working is how to set variables for a release pipeline run which is triggered by continous deployment. But that is more a Azure DevOps things than an UiPath one.

I would like to request some kind of best practice or recommendation from UiPath how to set this up. For example having the UiPath Pack task in the Build Pipeline and put the UiPath Deploy task in a release pipeline with several stages for TEST and PROD. How to make the pipeplines more dynamic, how to set variables, Continous Deployment enabled etc.

1 Like

Hello everyone,
We have just released a new version of the UiPath Azure Devops Plugin.

Whats new:

  • Support for deploying libraries
  • bug fixes
  • Introduced a new step to download CLI (optional)

Best regards
Thomas

1 Like

@ThomasStocker Since friday lunch time we are not able to use the UiPath Pack task in Azure DevOps build pipeline any more. We are getting the error: ##[error]Unhandled: connect ETIMEDOUT 137.116.207.86:443

Task version is 2.*. Any suggestions? There is no option to use an older version of the task. Quick help would be appreciated, because that breaks our release management completly.

Hi @ThomasStocker, same issue here as the user above me since friday, is there any way to resolve this?

@czonneveld I got a solution from UiPath Support today. Just add the Task UiPath Install Platform as first task in your pipeline. It will install some local tool on the deployment agent so the task is not trying to reach the external url https://www.myget.org/F/uipath-dev/. That caused the timeout for me, because it was blocked by our firewall.

after once using the UiPath install platform task everything works again. Could even disable the task again.

Check this link with the specific part for the UiPath Install Platform task: https://marketplace.visualstudio.com/items?itemName=uipath.vsts-uipath-package

for the future it would be great if such crucial changes are communicated better. It’s an easy to share information, but has huge effects on companies operations. For us this update just crashed the complete uipath release management for half a week.

5 Likes

Thank you! Fixed the issue in 1 minute.

Hi,

It works quite well, thanks for the update and the info! I’m still struggling with the versioning of the packages. I have two questions regarding the versioning.

  1. Could you maybe explain how the autoversion setting works? I tried to deploy a package 4 times and this are the version generated by the autoversion setting. I would prefer to have 1.0.4, 1.0.5, 1.06…

afbeelding

  1. When using the currentversion setting, it used the version presented in the project.json. The next time it will use the same version number again because the project.json does not get updated. Is there a way to also update the project.json or a different approach that would fix this?

Thanks in advance!

2 Likes

Hi @ThomasStocker,

Thanks for the release. Everything works really well!

I have a question:
The outcome of a published & deployed package (= Process name) on Orchestrator (“Processes” area) is named as {packageName} v{version} on {environment}. If we manually publish a package & deploy it for a process (without adding a Display name), the Process name is {packageName}_{environment}. Is there anyway to have the outcome process name as {packageName}_{environment} when using the Azure DevOps Integration plugin?

UiPath Integration Extension Build Agent Error
I have configured on premises service connection for orchestrator and also setup self hosted build agent. After that I have used classic editor in azure devops to run the build pipeline using UiPath tasks but on running build pipeline its throws an error “##[error]No agent found in pool XXXX which satisfies the specified demands: npm, Agent.Version -gtVersion 2.144.0”. Need help How to resolve this?

Hi,
I am not able to see UIPath orchestrator option in new service connection so that i can use to create a pipeline, can you please help me to know step by step how to add orchestrator to service connection?

Hi, did you make sure that the UiPath plugin has been added to your ADO instance?

Hi,
about (1):
I think we just generate some random version number here
about (2):
Typically you will increment the version when you change /edit your project and commit this to git. This would then lead to a new version in your project.json.
If there is no change, of course the version will not change as it is the same package

Hello @ThomasStocker
Thanks for the reply, It works well. thanks for the new release.

Thanks for solution! It helps us too.

Hello, I would like to ask for support in a particular scenario that does not allow me to work, I am using the plugin in my azure devops, it works correctly when I want to make the display to a main folder, but when I want to perform the display in a subfolder I don’t it works, example:

–OPS
-------- Process1
In the pipeline I put it to display in the OPS/Process1 folder but it shows me that it does not find said folder

Could you help me, thank you very much