Digging deeper via numerous community posts, I was able to confirm that our CI server(s) will definitely require a dedicated Ready API license to invoke our existing SoapUI-based functional test scripts.
Tim
Tim ,
I faced similar kind of situation when out jenkins server was running under differnt account and i installed soapUI under differnt account . As i have already activated the license copying and al other things did not work . So i open the case with support and got my license deactivated . after that i did intsall on linux under the same account which jenkins uses for running the job.
is it the case that we would need a license for the system responsible for developing the scripts and another for the system responsible for executing them?
As i have fixed license so i did have differnt license on devmachine and jenkin machine.
I am not sure if it helps in your case.
Thanks
Vk
Hey Vk,
Thanks a lot for the feedback and for providing a potential solution for our licensing predicament. I was considering taking that very same route, the only issue that I feared was that I would no longer have an active license for my test script development system (since it would require deactivation and transferral to our Jenkins executor(s) instead).
As you did, I will try and work with the Support team to determine what our available options are. And thanks again for the comments/suggestions Vk - very much appreciated.
Best Regards,
Tim
Digging deeper via numerous community posts, I was able to confirm that our CI server(s) will definitely require a dedicated Ready API license to invoke our existing SoapUI-based functional test scripts.
Tim
Het Tim and Vk,
I see you both have implemented Ready API- Jenkins for CI in your organization.I am looking into how this is done and pretty much stuck.Will you be able to give some tips and tricks plus key bullets on where to start ?
