At the moment we are busy with setting up a continuous build Jenkins server with CODESYS 3.5. The Jenkins server calls a *.bat batch file to start the win PLC and the command-line command for starting the TestManager. We encounter two challenges at this point.
The first problem is when we start CODESYS Testmanager by Jenkins it will runs as a background process without a gui. This will result in a error, because the TestManager apparently needs a GUI. Is there any possibility like the scripting argument --noiUI to start the TestManager also without a GUI?
The second issue is how to return a exit code which indicate an error encountered during the execution of the TestScript. Now the TestManager returns always zero, even when a error has occurred.
Many thanks in advance,
Niels Brouwer
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
At the moment we are busy with setting up a continuous build Jenkins server with CODESYS 3.5. The Jenkins server calls a *.bat batch file to start the win PLC and the command-line command for starting the TestManager. We encounter two challenges at this point.
The first problem is when we start CODESYS Testmanager by Jenkins it will runs as a background process without a gui. This will result in a error, because the TestManager apparently needs a GUI. Is there any possibility like the scripting argument --noiUI to start the TestManager also without a GUI?
The second issue is how to return a exit code which indicate an error encountered during the execution of the TestScript. Now the TestManager returns always zero, even when a error has occurred.
Many thanks in advance,
Niels Brouwer
Anybody was able to solve this problem yet? I'm stuck with a similar issue and find no solution as --noUI is not supported for Test Manager.
Hello All,
we are also struggling with the same issue, can we start codesys test manager with CLI interface headless/ without UI?
This is preventing us to do CI from git for our test automation.