Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UiPath Jenkins Plugin publish Process when created with “Windows” Compatibility Failing #155

Open
suryavaranasi9 opened this issue Jun 20, 2023 · 2 comments
Labels
bug Something isn't working

Comments

@suryavaranasi9
Copy link

Jenkins and plugins versions report

Jenkins: 2.346.4.1

What Operating System are you using (both controller, and any agents involved in the problem)?

Windows Server 2016

Reproduction steps

  1. Building project / main.xaml in UiPath Studio using Windows compatibility
  2. Pushing to Github repository
  3. Adding Jenkinsfile to repository
  4. Jenkins builds gets started.
  5. Project / Package successfully pushed to Orchestrator
  6. Going to "Automations" tab option, selecting "Jobs", Clicking "Start" option button
  7. Selecting "Process" name, selecting "runtime" and "priority" options, passing necessary arguments.
  8. Clicking on "Start" button

Expected Results

Process to start in UiPath and run the package/project

Actual Results

We are using Jenkins for deployments, and is using 2.11 version of plugin. Studio's and Orchestrator are on version 22.10.x.
When we are deploying Windows Legacy processes, deployment is being successful and automations are running fine.
But when we are deploying "Windows" processes, deployment is being successful but the automations are failing with an error.

Error message:
RemoteException wrapping System.IO.FileNotFoundException: Could not load file or assembly 'XXXXXX' , Culture=neutral, PublicKeyToken=null'. The system cannot find the file specified.
at System.Reflection.RuntimeAssembly.InternalLoad(ObjectHandleOnStack assemblyName, ObjectHandleOnStack requestingAssembly, StackCrawlMarkHandle stackMark, Boolean throwOnFileNotFound, ObjectHandleOnStack assemblyLoadContext, ObjectHandleOnStack retAssembly)
at System.Reflection.RuntimeAssembly.InternalLoad(AssemblyName assemblyName, RuntimeAssembly requestingAssembly, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, AssemblyLoadContext assemblyLoadContext)
at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyName(AssemblyName assemblyName)
at UiPath.Executor.WorkflowLoader.GetWorkflowFromXamlPath(String assemblyName, String xamlPath)
at UiPath.Executor.WorkflowLoader.LoadWorkflow(String xamlPath, String compiledWorkflowAssemblyName)
at UiPath.Executor.WorkflowRuntime.Load(String workflowFile, String compiledWorkflowAssemblyName)
at UiPath.Executor.WorkflowRuntime.Load(String workflowFile)
at UiPath.Executor.RobotRunner.InitWorkflowApplication()
at UiPath.Executor.RobotRunner.ExecuteJob()

Anything else?

No response

@suryavaranasi9 suryavaranasi9 added the bug Something isn't working label Jun 20, 2023
@derrickserbia
Copy link

Hi @suryavaranasi9, our team also uses this plugin and just ran into this error. Were you able to run the process if you Published from Studio and upload the package manually?

@suryavaranasi9
Copy link
Author

Hi @derrickserbia, YES manual steps are running fine. Publishing from Studio and upload the nuget package to Orch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants