Publish Packages to orchestrators with Azure DevOps

great detailed description…


great tutorial ! thanks for your help.
It’s working fine for the pipeline, however i’ve this issue : 2020-01-29T13:47:19.5435953Z ##[error]Unable to deserialize the response. when I would like to release on a community Orchestrator.

Does any one already success to push the package to Orchestrator without any issue ? of fix this one ?

Thanks in advance.

@Stephu Thanks for the nice tutorial!

I got some questions:

  1. Would you recommend creating a new pipeline for each git repository?
  2. Any updates on when the autoversioning feature works again?
  1. What are the alternatives? One pipepline for all packages? How would you handle that in the case you have only a change on one package? The “unit” for package upload is a single package. You cannot upload multiple packages at once.
  2. No for uipath this azure devops module has no priority. Up to all the ask for these multiple outstanding features🤓 Maybe they work faster for a new release in the case a lot person are asking.

Thanks for the quick reply!

  1. Currently we use only one pipeline and manually change the git repository and package version for each time we run the pipeline. So we have to start the build manually, but that’s good to have some quality gate at first. When the autoversioning was working that was really nice and easy to use. now with changing the version number everytime it sucks…
    I think having for each repo a pipeline just blows up azure devops alot. currently it would be ok with 20-30 repos, but after full scaling it would be a mess to handle 200 pipelines, or?
  2. Thanks for the information, that’s sad.
  1. Good point. At the moment I disabled the pipeline because of all this issues. I upload unprofessionally by hand.(at the moment i have 40 packages, and this works quite well) But when everything is running I’m planning to workout one pipeline use this as template to create all others. From my point of view there are also other points which I know from Java or C# programming like writting unit test, static code analyses with shared configurations…
1 Like

I’m getting the following error, when trying to deploy.

##[error]The operation returned an error: 1000: Invalid credentials, failed to login.

I’ve used both AD, and user and password options. For username and password I tried both email and username. But got the same error. I’m trying to deploy to cloud orchestrator.
Any help would be appreciated.

Does this user has admin rights on orchestrator?

@Stephu Yea, one is the owner, I also tried an admin and a user account

@Stephu , nice article . I have configured the pipeline the same way mentioned . But the package is shipped to default tenant , It is not shipping to the tenant i have mentioned . I have access to multiple tenant orchestra tor. Please suggest . I had set the tenant name in the Orchestrator tenant column .

1 Like


Can someone share similar details with TFVC Repo. i.e. Creating Build and release pipeline.

I can build the pipeline but unable to move ahead with release.

Hi @Ilavarasi_T,

I had similar case with you.
Are you already solved your case ?
I will appreciate if you share your solution to me.


No… I’m searching an alternative because there is no progress on this module.

@Stephu Could you please explain how we can connect Agent to [orchestrator] ? Once I add Uipath pack as a task I did’t get the OrchestartorPath in the variable window !

I do not understand you question? The path you have to define by your own

Thanks a lot for the prompt response! What I meant that the OrchestratorPath variable is not visible when I need to fill my own value? So do we need to create this variable ?

Yes you have to create all these variables by yourself

Firstly an Amazing Article to help with Pipelines via DevOps.

I followed the steps and created a PipeLine.

I have hardcoded my project version to be 1.0.0

When i save and Run the Pipeline.I get below error.Can you help ?

Error Details:

Importing module D:\a_tasks\UiPathPackage_0e237901-8ece-4bc9-bedf-05ed7f0e98d5\1.0.51\RobotScripts\RobotExecutor-PublicModule.psd1

##[warning]Some imported command names contain one or more of the following restricted characters: # , ( ) {{ }} & - / \ $ ^ ; : " ’ < > | ? @ ` * % + = ~

Importing module D:\a_tasks\UiPathPackage_0e237901-8ece-4bc9-bedf-05ed7f0e98d5\1.0.51\RobotScripts\UiPathPackage-Module.psd1

14.05.2020 07:26:25: Found different platform version

Platform version: 18.3.2

Setup msi name: UiPathStudio.msi

14.05.2020 07:26:25: Stopping service: UiRobotSvc

14.05.2020 07:26:26: Stopping process: UiPath.Executor.exe

14.05.2020 07:26:26: Stopping process: UiRobot.exe

14.05.2020 07:26:26: Uninstall options: ifdifferent → Uninstall platform: True

14.05.2020 07:26:26: Install platform: True

14.05.2020 07:26:26: Downloading Setup from to d:\a_temp\r26023\UiPathStudio.msi

14.05.2020 07:26:26: Start Invoke-DownloadMsiFromUrl

14.05.2020 07:26:26: Downloading from to d:\a_temp\r26023\UiPathStudio.msi

14.05.2020 07:26:29: End Invoke-DownloadMsiFromUrl

14.05.2020 07:26:29: Start Invoke-Install

14.05.2020 07:26:29: ------Starting Uninstall

14.05.2020 07:26:29: Determining IdentifyingNumber for installed ‘UiPath’ product

14.05.2020 07:28:39: No application found for uninstalling

14.05.2020 07:28:39: ------Finished Uninstall

14.05.2020 07:28:39: ------Start installing Studio

14.05.2020 07:28:39: Installing product from d:\a_temp\r26023\UiPathStudio.msi

14.05.2020 07:28:39: msiexec /qn /i “d:\a_temp\r26023\UiPathStudio.msi” ADDLOCAL=DesktopFeature,Studio,Robot,RegisterService,Packages /L*V d:\a_temp\l\platformInstall.log

14.05.2020 07:29:35: ------Finished installing Studio

14.05.2020 07:29:35: Start service UiRobotSvc with retry 5

14.05.2020 07:29:35: Service status: Running

14.05.2020 07:29:35: End Invoke-Install

14.05.2020 07:29:35: Running pack with the arguments: -pack d:\a\1\s\project.json -o d:\a\1\a -v 1.0.0

Error detecting project version

##[error]Pack command generated no result. Might be a problem with the specified parameters.[d:\a\1\s | 1.0.0 | | d:\a\1\a]strong text

Thanks @Stephu for the great article.
I have few doubts in release step, a) While providing the username and password should we need to provide the orchestrator username and password? I got confused when you mentioned to create a user name in orchestrator. Also I couldn’t figure out the password in the uipath orchestrator while creating the user name.

Appreciate any help on this.
This is the error I am getting while I run the release (Deploy)

2020-05-27T10:29:18.8341876Z 27.05.2020 10:29:18: Deploying d:\a\r1\a/UIPathSource-CI (1) to UiPath
2020-05-27T10:29:20.5856844Z ##[error]Operation returned an invalid status code ‘NotFound’
2020-05-27T10:29:20.6520564Z ##[section]Finishing: UiPath deploy

1 Like

if you are using username and pw to authenticate towards Orchestrator, an existing Orchestrator user+pw is required to login. For this purpose you might want to create a separate ‘technical user’ on Orchestrator like e.g. ‘AzureDevops’ so that you can easily identify within the Orchestrator logs, where a certain package came from.
We are currently working on a new version of this plugin, which will allow you to authenticate via API token, and which will also allow you to trigger test execution on Orchestrator. This plugin will most likely be available within the next few weeks.