Create your first automation in just a few minutes.Try Studio Web →
by UiPath
8
Connector
494
Hi Tomas,
I have the following problem:
Obtained Jenkinsfile from b56bd06273b4cdc374d737147b40d4c220c99045
Running in Durability level: MAX_SURVIVABILITY
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
WorkflowScript: 89: Invalid parameter "traceLevel", did you mean "credentials"? @ line 89, column 10.
traceLevel: 'None',
^
WorkflowScript: 90: Invalid parameter "entryPointPaths", did you mean "environments"? @ line 90, column 10.
entryPointPaths: 'Main.xaml'
^
2 errors
at org.codehaus.groovy.control.ErrorCollector.failIfErrors(ErrorCollector.java:310)
at org.codehaus.groovy.control.CompilationUnit.applyToPrimaryClassNodes(CompilationUnit.java:1085)
at org.codehaus.groovy.control.CompilationUnit.doPhaseOperation(CompilationUnit.java:603)
at org.codehaus.groovy.control.CompilationUnit.processPhaseOperations(CompilationUnit.java:581)
at org.codehaus.groovy.control.CompilationUnit.compile(CompilationUnit.java:558)
at groovy.lang.GroovyClassLoader.doParseClass(GroovyClassLoader.java:298)
at groovy.lang.GroovyClassLoader.parseClass(GroovyClassLoader.java:268)
at groovy.lang.GroovyShell.parseClass(GroovyShell.java:688)
at groovy.lang.GroovyShell.parse(GroovyShell.java:700)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.doParse(CpsGroovyShell.java:142)
at org.jenkinsci.plugins.workflow.cps.CpsGroovyShell.reparse(CpsGroovyShell.java:127)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.parseScript(CpsFlowExecution.java:561)
at org.jenkinsci.plugins.workflow.cps.CpsFlowExecution.start(CpsFlowExecution.java:522)
at org.jenkinsci.plugins.workflow.job.WorkflowRun.run(WorkflowRun.java:327)
at hudson.model.ResourceController.execute(ResourceController.java:97)
at hudson.model.Executor.run(Executor.java:429)
Finished: FAILURE
Hi Thomas,
Getting a problem where no matter what access type (refresh token or external application) or URL we use, Jenkins is reporting that it cannot connect to the cloud orchestrator. For example,
Failed to run the command. Could not connect to Cloud Orchestrator, Refresh Token: ***, Tenant: ***, Account Name: ***, OrganizationUnit: ***.
Please make sure that the provided URL (https://cloud.uipath.com/) is correct, available from your build agent, and not blocked by a firewall.
If the Orchestrator is using a self-signed SSL certificate, make sure that the build agent trusts it. Ensure that all the steps at https://docs.uipath.com/orchestrator/docs/self-signed-certificates were correctly followed when creating the certificate.
I can see no obvious firewall problems, and have tried changing the URL to include the full tenant name etc, but still nothing.
Is there something obvious we are missing?
Thanks
Gareth
Hi Thomas,
We're experiencing an issue with the packer, where a folder doesn't seem to exist within the workspace folder. Does the plugin require a specific workspace in order to access the UiPath CLI tools?
[Pipeline] stage
[Pipeline] { (Build)
[Pipeline] echo
Building in C:\data\jenkins_home\workspace\xxxxx
[Pipeline] UiPathPack
Expected plugin jar path on Jenkins master: C:\data\jenkins_home\plugins\uipath-automation-package\WEB-INF\lib\uipath-automation-package.jar, extracting...
[net461] $ C:\data\jenkins_home\workspace\xxxxx@tmp\cli-1.0.8136.25036\lib\net461\uipcli.exe run C:\data\jenkins_home\workspace\xxxxx@tmp\uipcliargs2940789323837720959
[...]
FAILED: Job 'xxxxx [10]' (xxxxx)
[...]
java.io.IOException: Process working directory 'C:\data\jenkins_home\workspace\xxxxx@tmp\cli-1.0.8136.25036\lib\net461' doesn't exist!
at hudson.Proc$LocalProc.(Proc.java:252)
at hudson.Proc$LocalProc.(Proc.java:223)
at hudson.Launcher$LocalLauncher.launch(Launcher.java:997)
at hudson.Launcher$ProcStarter.start(Launcher.java:509)
at com.uipath.uipathpackage.util.Utility.execute(Utility.java:69)
at com.uipath.uipathpackage.UiPathPack.perform(UiPathPack.java:150)
at jenkins.tasks.SimpleBuildStep.perform(SimpleBuildStep.java:123)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:101)
at org.jenkinsci.plugins.workflow.steps.CoreStep$Execution.run(CoreStep.java:71)
at org.jenkinsci.plugins.workflow.steps.SynchronousNonBlockingStepExecution.lambda$start$0(SynchronousNonBlockingStepExecution.java:47)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
[Bitbucket] Notifying commit build result
[Bitbucket] Build result notified
Finished: FAILURE
Hi,
My client doesn't whitelist the below urls
BuildFeedModel("https://www.myget.org/F/workflow/", "Official"),
BuildFeedModel("https://gallery.uipath.com/api/v2", "Connect"),
BuildFeedModel("https://api.nuget.org/v3/index.json", "nuget.org")
Instead when we want to downlaod any new packages from studio, we usually hit our nexus repository and it is configured to hit the external feeds to download the library to nexus which is then downloaded to studio/users machine.
So, do we have any configuration in the uipath jenkinsplugin where we can update the feed source instead of poinitng to the above sources.
Thanks in advance.
Hi,
I am facing issue with UiPath Deploy, as it is trying to create new process for every build and orchestrator is throwing error "Make sure the $process is not already deployed to one of the robots in the environment"
The issue is identified post the Jenkins URL is converted to HTTPS, earlier did not face issue with process creation for each build.
Hi Thomas,
How to get auto version build number in print variable?If i want to create a tag with version .
You could create your own build version number and just use this within your Pack step, this way you have the number under full control.
if you want to use the automatically generated build number from the package, you could extract it from the created nugetpackage.
A typical nugetpackage has the following naming convention:
my_package.1.0.81087863.nupkg
so if you simply extract the number from the package name you can reuse it.
Hi Thomas,
Can it build a package from source code in github and then deploy packge from git to orchestrator, if so what should be given as 'Project(s) path' if using git as source code placeholder.
Thanks
Hi,
you would use the path to the project json checked out locally from Git
Hi Thomas,
what is the api used for creating package from git sourcecode.
Thanks.
Hello,
for this we use the Studio packager, which we included within our plugin. If you want to use the packaging functionality without the plugin, pls refer to the robot commandline interface
https://docs.uipath.com/robot/docs/robot-command-line-interface
The below tasks are not present in the Add Build Step when trying to create a new Freestyle JOb:
UiPath Run Job
UiPath Deploy
UiPath Run tests
Hi Debash, did you upgrade the plugin to the latest version?
Did you make sure to have the dependencies in the Jenkins doc stated to be met?
https://plugins.jenkins.io/uipath-automation-package/#dependencies
BR
Hi Thomas!
I want to pack few projects locally without orchestrator but before calling plugin's directives in pipelined script I have to clear NuGet's cache and global packages under .nuget\packages\.
Does plugin use NuGet.Config file for downloading dependencies from project.json or any other mechanism?
Hi Aliaksandr,
we do not use local nuget.config.
We use the following feeds for dependencies:
BuildFeedModel("https://www.myget.org/F/workflow/", "Official"),
BuildFeedModel("https://gallery.uipath.com/api/v2", "Connect"),
BuildFeedModel("https://api.nuget.org/v3/index.json", "nuget.org"),
I am getting below error. Please help me
ERROR: Running on non-Windows operating systems is currently not supported for UiPath build steps.
Hello Ravindra.
The error message is pretty clear here:
: Running on non-Windows operating systems is currently not supported for UiPath build steps.
This means you build agent will have to be a Windows machine as our components run on Windows only.
So if your nomal build agents are non-windows you can simply add a single build agent based on Windows, where you can execute the UiPath steps.
Hi Thomas,
This plugin is working for me (UiPath Pack I'm using for build and post-build i'm using UiPath Deploy), but I'm facing one challenge the JSON file is not updating properly and also how I can set the "Use the version specified in the project file" in the version method. could you please advise me on the same?
Thank You!
Hi Alwin,
if you are using pipeline script and want to use the package version defined in your project, pls try the following syntax:
version: CurrentVersion()
Technical
Updated
December 20, 2021Works with
Studio: 19.4 - 22.10
Application
Support
Email: https://www.uipath.com/company/contact-us/contact-technical-support
Link: https://www.uipath.com/company/contact-us/contact-technical-supportUiPath Standard Support, see your Service Agreement
Resources