Activate Runtime Engine

This is a companion discussion topic for the original entry at

Hello Guys @community_admin,
you said:

Create an offline license with a computer ID that can be viewed in the Katalon Studio Activation window. The computer registered with Katalon Server is added to the Registered Machines list.

  1. what if i don’t have such access to machine that will execute tests? (linux node building machines)
  2. what will be with docker? how to use licenses there?

hi @devalex88,

I am in the same problem

Thanks for your response

1 Like

@Andrej_Podhajsky, @Dino For Docker containers without internet access, you will need to install an offline license server (it’s not publicly available for downloading yet). For Docker containers with internet access, please contact - pricing will be based on the maximum number of concurrent executions.

Thanks @devalex88 but they do not answer …

Sorry for that - please PM me the email address and I will remind them.


How can I use the RE on a remote jenkins machine?
I couldn’t find any information about that.
I have a Jenkins job that runs ok with KS 6.3.3, but doesn’t work win 7.x.x.
Thank you.

any code examples on using RE within Docker image??

it looks to me that Katalon started charging people before figuring out how everything will work…
very disappointing… and to not have a free way to execute tests in command line enviornment is disturbing… pretty much “Katalon Studio will stay Free” has gone trough the window since if you can create tests and cannot execute them it is pretty much useless…

Katalon Studio is sticking with frameworks that work and are free (Selenium/Appium/Cucumber) but not allowing execution of these tests for free… … very very disturbing…

I know people complained but I will do it again… adding new features and charging for them is OK… taking features that were free and claimed to be free and start charging for them is equivalent to black mail…

@devalex88 to repeat my question… any examples on how to use RE within docker container…


Hello Rasko

Not sure if this Katalon Studio Docker Image is what you are looking for. But I’ll give it a try anyway.


Hello there,
‘Currently, free license is not available for Runtime Engine.’ means even within the evaluation period we can’t evaluate Katalon Studio Engine ?

Hello @evaie

For evaluation, every Katalon account registered with a business email is eligible for a 30-day trial of Kataton Studio Enterprise and Katalon Runtime Engine.


@Jass @devalex88 Can we use Katalon Jenkins Plugin with Katalon Runtime engine ?

I tried to use the same with Runtime engine by adding runtime engine path in Use pre-installed Katalon Studio field and it keeps on looking for katalon.exe instead of katalonc.exe

Is there something I need to change. I am sure there should be some way to make this work.

Source code for this job is defined in Source Code Management step :

Hi @manpreet.mukkar,

You should specify absolute path in Use pre-installed Katalon Studio input path as tilde (~) cannot be expanded correctly. Also, please make sure the provided path is the directory containing the katalonc executable (with trailing .exe extension on Windows).

Secondly, you are missing a hyphen (-) before retry=0 in Command arguments input. It should be -retry=0 instead.

Hope this helps!


make sure you are using the latest version of the plugin for jenkins.
if still not working it may be a bug

1 Like

@sonpham I tried the same but I am getting below error.

Using Katalon Studio at /home/manpreet/Katalon_Studio_Engine_Linux_64-7.1.0/katalonc
Making driver executables...
Drivers folder at: /home/manpreet/Katalon_Studio_Engine_Linux_64-7.1.0/katalonc/configuration/resources/drivers
java.nio.file.FileSystemException: /home/manpreet/Katalon_Studio_Engine_Linux_64-7.1.0/katalonc/configuration/resources/drivers: Not a directory
   at sun.nio.fs.UnixException.translateToIOException(
   at sun.nio.fs.UnixException.rethrowAsIOException(
   at sun.nio.fs.UnixException.rethrowAsIOException(
   at sun.nio.fs.UnixFileAttributeViews$Basic.readAttributes(
   at sun.nio.fs.UnixFileSystemProvider.readAttributes(
   at sun.nio.fs.LinuxFileSystemProvider.readAttributes(
   at java.nio.file.Files.readAttributes(
   at java.nio.file.FileTreeWalker.getAttributes(
   at java.nio.file.FileTreeWalker.visit(
   at java.nio.file.FileTreeWalker.walk(
   at java.nio.file.FileTreeIterator.<init>(
   at java.nio.file.Files.walk(
   at java.nio.file.Files.walk(
   at com.katalon.utils.KatalonUtils.makeDriversExecutable(
   at com.katalon.utils.KatalonUtils.executeKatalon(
   at com.katalon.jenkins.plugin.ExecuteKatalonStudioUtils$
   at com.katalon.jenkins.plugin.ExecuteKatalonStudioUtils$
   at com.katalon.jenkins.plugin.ExecuteKatalonStudioUtils.executeKatalon(
   at com.katalon.jenkins.plugin.ExecuteKatalonStudioTask.perform(
   at hudson.tasks.BuildStepMonitor$1.perform(
   at hudson.model.AbstractBuild$AbstractBuildExecution.perform(
   at hudson.model.Build$
   at hudson.model.Build$BuildExecution.doRun(
   at hudson.model.AbstractBuild$
   at hudson.model.Run.execute(
   at hudson.model.ResourceController.execute(

Build step 'Execute Katalon Studio Tests' marked build as failure
Finished: FAILURE

Try removing /katalonc from the pre-installed path.

1 Like

@ThanhTo i think the gui of the plugin need some love … the fields descriptions are a bit missleading

it is not obvious where is expecting a root path, location of an an executable or a version (altough the question mark may show some relevant info)

e.g path to preinstaled katalon may be more suggestive instead of use blah blah

1 Like

@ThanhTo So If I remove the /katalonc from the path and only keep the Katalon Runtime engine path it tries to find katalon instead of katalonc

sh: 1: /home/manpreet/Katalon_Studio_Engine_Linux_64-7.1.0/katalon: not found
Build step 'Execute Katalon Studio Tests' marked build as failure
Finished: FAILURE

I think thats how Plugin is build as it was for Studio

I also tried this approach by giving the absolute path without the executable in the preinstalled path and then the command field giving the executable name

@manpreet.mukkar kindly check an post an sshot from jenkins config > plugin section so we can figure out what version do you use and what is available

just for my mind sanity, please

@Ibus Its 1.0.21, This is the latest available version.