Closed GeneralMidiRotkiv closed 2 months ago
Hi, sorry for the late reply.
There is a difference in the tool configuration between the two plugins. The old plugin needs just a path to the tool folder and will search for the executable itself, while this plugin needs the full path to the executable.
We might need to change the error message, as it is is misleading.
That fixed it for me, thanks! Well, the error message would have helped if I had cought the "executable path", but I guess I was too focused on it working in the previous version with the path to the folder that I didn't realise it. It also doesn't help that both plugins show up under "ecu.test installations" in Manage Jenkins > Tools as it is not clear which is which. But these are problems that will be avoided once only the newest plugin is installed.
Derived a new issue from it. So will close this bug.
Describe the bug
I am in the process of switching from the old version of the plugin to this one. While the old plugin works as expected, the new version does not seem to find the executable in the filepath provided by me. Every time I start the job I get the following error:
org.jenkinsci.plugins.workflow.actions.ErrorAction$ErrorId: 9ae0d12b-bafa-4bce-99fa-b614b191e89a 12:51:46 java.lang.IllegalArgumentException: Tool executable path of 'ecu.test2': 'C:\Program Files\ecu.test BMW 2024.2' does not contain a tracetronic tool!
However, the provided path is the same as the one the old plugin is using, working fine
Steps to reproduce
Install Jenkins version 2.452.1 and the ecu.test execution plugin. In the "Tools" setting, set the path to the ecu.test executable and run a basic pipeline (e.g ttStartTool)
Expected behavior
Jenkins should be able to start ecu.test on the machine
Versions
Additional context
No response