Pabot fails to execute robot through Jenkins

[Prashant1781]

Objective is to run test cases/suites in parallel using Pabot configured in Jenkins pipeline. The below command configured in Jenkins fails to run/execute robot: python3 -m pabot.pabot --testlevelsplit -v V_ENVIRONMENT:$environment -v V_REMOTE_URL:$remoteURL -v V_BROWSER:$browser -v V_DESIRED_CAPABILITIES:$desiredCapabilities --nostatusrc --outputdir <Project Name>/reports/ *-<Path>/.robot This command starts pabot with multiple processes, creates workspace + seperate folders for robot output files for each process but fails to write/create the files: output.xml, log.html, report.html at the project level folder. The process specific folders has error logged "/bin/sh: 1: robot: not found" . It appears that the pabot command fails to locate robot script and execute it

[linh-eureka]

Objective is to run test cases/suites in parallel using Pabot configured in Jenkins pipeline. The below command configured in Jenkins fails to run/execute robot: python3 -m pabot.pabot --testlevelsplit -v V_ENVIRONMENT:$environment -v V_REMOTE_URL:$remoteURL -v V_BROWSER:$browser -v V_DESIRED_CAPABILITIES:$desiredCapabilities --nostatusrc --outputdir /reports/ *-/.robot This command starts pabot with multiple processes, creates workspace + seperate folders for robot output files for each process but fails to write/create the files: output.xml, log.html, report.html at the project level folder. The process specific folders has error logged "/bin/sh: 1: robot: not found" . It appears that the pabot command fails to locate robot script and execute it

Hi, I met the same issue, do you have some workaround for it?

@mkorpela Could you take a look?

[joonaskuisma]

Hi!

It does seem like Robot Framework isn’t found, or at least not directly callable.

Could you try running the following command in your pipeline to check?

robot --version

Does it work?