Deploy Uipath from Jenkins facing issue

Hello All,

Can you please help us on below query:

Below pipeline script included to deploy Uipath package from jenkins .
UiPathDeploy(environments: ‘IT_Jenkin’, folderName: ‘processes’, orchestratorAddress: ‘Orchestartor URL’, orchestratorTenant: ‘Default’, packagePath: ‘Local Pacakage path’,credentials: UserPass(‘RPAOrchestratorCredentials’))

Can you give more clear information on the Orchestrator FolderName to be provided.

Unable to build the project in jenkin due to parsing issue.Please find attached pic for more info.

We referred below url to integrate uipath with Jenkins:

Issue we are facing as below:

RPAdemo4 #42 Console [Jenkins]

Expected plugin jar path on Jenkins master: C:\Users*.jenkins\plugins\uipath-automation-package\WEB-INF\lib\uipath-automation-package.jar, extracting… Extracting cli to temp folder C:\Users*.jenkins\workspace\RPAdemo4@tmp…done! [net461] $ C:\Users*.jenkins\workspace\RPAdemo4@tmp\cli-1.0.7423.22942\lib\net461\uipcli.exe run C:\Users*.jenkins\workspace\RPAdemo4@tmp\uipcliargs892296028770225425 Failed to run the command: Microsoft.Rest.SerializationException: Unable to deserialize the response. —> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path ‘’, line 0, position 0. at Newtonsoft.Json.JsonTextReader.ParseValue() at Newtonsoft.Json.JsonTextReader.Read() at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter) at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)

Hi @a.kalpana5,

The folderName value is the name of the folder (19.10+) or the organization unit (pre-19.10).

You can find it in the top-right corner, once you log in (the screenshot is from 18.4, the 19.10+ UI looks a little bit different, yet it’s virtually the same).

If you do not have anything written over there, your pre-19.0 Orchestrator might not have organization units enabled, in which case please ensure that you have at least version 2.0.1 of the Jenkins plugin, (it was released just a couple of days ago and fixed a bug related to deployment on older Orchestrators with organization units disabled), and use an empty string as the folderName.

Thank you Alvinstanescu.
Can you also please let us know the fix for the issue which has been posted.


Now able to deploy the process from jenkins.