UiPath Azure Devops Integration

finally our pipeline is executed OK and the robot is published in our orchestrator. the last change we made was in the Uipath Deploy task, in the package path. we didn´t notice that the folders route wasn`t complete. thanks you so much!!

3 Likes

Hi Samantha,
deploying libraries is done via the existing ‘deploy’ step. You simply choose library as the output type.
Does this work for you or do you need additional assistance?

Michelle,
the next release of our plugins is right around the corner, ETA: begin of August. This new version will include an option to deploy to a specific folder feed.

Is the output type in the deploy step as well? I don’t see an option for that

Hi Samantha,
sry, my bad, this option is on the pack step:
image

1 Like

Oh okay, thanks!

I imagine you already got the answer but, just in case: No, it doesn’t. The Studio is independent to the CI/CD process. The only thing you have to be sure is that you have version control setup for the process you are developing, which works for both Pro and Standard (and in any case, you could do the commit and pushing from the command line)

1 Like

We have been using azure dev ops to deploy our processes to orchestrator for a few months now. All of a sudden, only when pushing to one tenant but not the others, we get this error:
System.InvalidOperationException: Microsoft.Rest.HttpOperationException: Operation returned an invalid status code ‘Conflict’

Same process being pushed to both tenants, one is just fine the other gives this error. Does anyone know what would be causing this? TIA
@ThomasStocker

Hi Samantha,
could you pls share the entrie console log output here?

Hi Thomas, here it is:

2021-08-06T14:20:12.3426398Z ##[section]Starting: UiPath Deploy

2021-08-06T14:20:12.3621855Z ==============================================================================

2021-08-06T14:20:12.3622357Z Task : UiPath Deploy

2021-08-06T14:20:12.3622832Z Description : Deploys a UiPath NuGet package onto UiPath Orchestrator.

2021-08-06T14:20:12.3623138Z Version : 2.4.1786427

2021-08-06T14:20:12.3623364Z Author : UiPath

2021-08-06T14:20:12.3624132Z Help :

2021-08-06T14:20:12.3624425Z ==============================================================================

2021-08-06T14:20:13.5608887Z CLI downloaded successfully, extracting…

2021-08-06T14:20:13.5902589Z (node:6124) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.

2021-08-06T14:20:16.1891955Z Caching tool: uipcli 1.0.7881-13724 x64

2021-08-06T14:20:17.0423685Z [command]D:\a_temp\sm58fy2mi\lib\net461\uipcli.exe run D:\a_tasks\UiPathDeploy_72167370-9f1d-47d5-be00-6f2554c20001\2.4.1786427\DeployOptions.json

2021-08-06T14:20:23.8077897Z Deploying package -.20210806.3.0 to tenant *** on https://cloud.uipath.com/***…

2021-08-06T14:20:24.1422004Z FeedId for FolderId 396604: .

2021-08-06T14:20:24.1475145Z Deploying project(s) D:\a\r1\a***-20210806.3.0.nupkg to https://cloud.uipath.com/ and tenant *** to Package feed.

2021-08-06T14:20:24.6686413Z Status: OK

2021-08-06T14:20:24.6688423Z Key: D:\a\r1\a*-*.20210806.3.0.nupkg

2021-08-06T14:20:24.6689485Z Body: {“Id”:“-”,“Version”:“20210806.3.0”}

2021-08-06T14:20:25.2315969Z Process will be deployed in modern folder.

2021-08-06T14:20:25.2371617Z No process exists for this package. Will create one.

2021-08-06T14:20:25.8064692Z System.InvalidOperationException: Microsoft.Rest.HttpOperationException: Operation returned an invalid status code ‘Conflict’

2021-08-06T14:20:25.8066552Z at UiPath.Web.Client21_4.Releases.d__6.MoveNext()

2021-08-06T14:20:25.8067332Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8067843Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8068362Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8068943Z at UiPath.Orchestrator.Client.Util.ExceptionsHandler.d__1`1.MoveNext()

2021-08-06T14:20:25.8069522Z {“message”:“The name - is already used.”,“errorCode”:1001,“resourceIds”:null}

2021-08-06T14:20:25.8070116Z at UiPath.Orchestrator.Client.Util.ExceptionsHandler.d__1`1.MoveNext()

2021-08-06T14:20:25.8070654Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8071133Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8072180Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8072712Z at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)

2021-08-06T14:20:25.8073200Z at UiPath.Orchestrator.Client.Endpoints.Releases.d__7.MoveNext()

2021-08-06T14:20:25.8073672Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8074165Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8074696Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8075199Z at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)

2021-08-06T14:20:25.8075714Z at UiPath.CommandLine.Services.Impl.DeployService.d__9.MoveNext()

2021-08-06T14:20:25.8076219Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8078472Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8078991Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8079515Z at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)

2021-08-06T14:20:25.8080014Z at UiPath.CommandLine.Services.Impl.DeployService.d__7.MoveNext()

2021-08-06T14:20:25.8080499Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8080989Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8082415Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8082999Z at UiPath.CommandLine.Services.Impl.DeployService.<>c__DisplayClass3_0.<b__2>d.MoveNext()

2021-08-06T14:20:25.8083519Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8084179Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8084712Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8085279Z at UiPath.CommandLine.Extensions.EnumerableExtensions.<>c__DisplayClass0_0`2.<b__2>d.MoveNext()

2021-08-06T14:20:25.8086286Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8086802Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8087315Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8087834Z at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)

2021-08-06T14:20:25.8088320Z at UiPath.CommandLine.Extensions.EnumerableExtensions.d__0`2.MoveNext()

2021-08-06T14:20:25.8088846Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8089332Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8089871Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8090386Z at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)

2021-08-06T14:20:25.8090847Z at UiPath.CommandLine.Services.Impl.DeployService.d__3.MoveNext()

2021-08-06T14:20:25.8091475Z — End of stack trace from previous location where exception was thrown —

2021-08-06T14:20:25.8092253Z at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

2021-08-06T14:20:25.8093442Z at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

2021-08-06T14:20:25.8093957Z at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)

2021-08-06T14:20:25.8094468Z at UiPath.CommandLine.Services.Impl.OptionsParser.d__6.MoveNext()

2021-08-06T14:20:25.8505725Z ##[error]Error deploying package: Error: The process ‘D:\a_temp\sm58fy2mi\lib\net461\uipcli.exe’ failed with exit code 1.

2021-08-06T14:20:25.8583716Z ##[section]Finishing: UiPath Deploy

It does say “name is already being used” there, but we are just trying to update the bot so it will already exist

Samantha,
we assume this happens because there is already a package on this tenant with the same name and package version.
Could you try to use a different version when packaging the project? (e.g. autoversion)

hey @ThomasStocker,

The way we do versioning is .0. and the build number is yyyymmdd.rev. So the first build today is 20210810.1, the second is 20210810.2, etc. So the version is never the same whenever we do a new build, and these releases are being run right after a new build, so with a new build number and version

We do this the same way in our dev environment, and haven’t had this error or any issues

Hi,
I am trying to deploy a package to Orchestrator and I am facing an error to create the release.

The error is UiPath.Orchestrator.Client.Exceptions.OrganizationUnitInitializationException:
*** Folder *** could not be found. Please make sure that this folder exists on Orchestrator,***
*** that your user has at least one role with the Folder View and SubFolder View permissions,*** *** and that the user has permissions to access the folder.***

We are working with a Orchestrator on-premisse, using a Classic Folder, still having Default folder.

Do you have any idea ?

1 Like

Samantha,
we were not able to reproduce the mentioned behavior internally which is why I would suggest you show us the problem live in a zoom session.
Therefore pls connect via thomas.stocker[at]uipath.com so that we can setup a call.

Alexandre,
could you pls share a screenshot of Orchestrator folder structure?

Thomas,
Of course.
Please have a look on still.
We are still using the folder Default.

Acctually, maybe, I found the issue .
Failed to run the command. Could not connect to Orchestrator: https:/my-orchcestrator-URL/ , Tenant: ***, Username: ***, Password: ***, OrganizationUnit: ***, UseWindowsCredentials: False.

The service connection is done using Basic Authentication mode.

My Orchestrator is on Premisse,

Thank you so much, I sent you an email!

Most likely this is the error and I did not find a solution yet to it

2021-08-12T13:06:04.3450747Z Found tool in cache: uipcli 1.0.7881-13724 x64
2021-08-12T13:06:04.3509550Z [command]C:\azagent\A3_work_tool\uipcli\1.0.7881-13724\x64\uipcli.exe run C:\azagent\A3_work_tasks\UiPathDeploy_72167370-9f1d-47d5-be00-6f2554c20001\2.4.1786427\DeployOptions.json
**2021-08-12T13:06:07.2701201Z Failed to run the command. Could not connect to Orchestrator: https:/my-orchcestrator-URL/ , Tenant: ***, Username: ***, Password: ***, OrganizationUnit: *, UseWindowsCredentials: False.
2021-08-12T13:06:07.2703035Z Please make sure that the provided URL (https://my-orchcestrator-r.com/) is correct, available from your build agent, and not blocked by a firewall.
2021-08-12T13:06:07.2704100Z If the Orchestrator is using a self-

Does anybody has faced this as well ?

I found a solution.

I decided to run once with one admin account from Orchestrator.

maybe the user I was using did not have permission, or any character from the password was causing problems

Then it worked fine to me.